When using the “Push Package Build Information to Octopus” step, my package only includes information about the commits associated with the build, and not the work-items: when I open the package details screen on octopus deploy, there are only commit details.
As a consequence, the release note is empty: there a no work items linked. As stated in the docs, I expected that the work items could be automatically associated.
In the build details in Azure Devops, I can see that multiple work items are associated with the build.
Based on OctoTFS source code it seens the buildinformation.json file generated by the “Push Package Build Information to Octopus” does not generate work item information, only information about commits.
The Publish Release Notes on Create Release step, which is now considered legacy, supports publishing work item information when creating releases.
Is it a known limitation ?
Edit: I can browse the code responsible for grabbing related work items for the build in the Create Release step. This code could be used in the Publish Build Information step to create a workItem propery in buildinformation.json and publish work item information for the build.
For now I will certainly revert to the previous release notes when creating the release instead of the publish build information step.