Prerequisites
The enhancement
What is the problem this solves or benefit it gives
At the moment release creation is a black box, especially the processing and attachment of build information (package metadata). This means that if work items aren't parsed, confirmed and attached there is no explanation as to why not.
Proposed solution
Update the release creation so the issue tracker extensions can return information about the work item Ids they parsed out of the commits and which of those did/didn't exist in issue tracker (e.g. Jira, GitHub, or ADO).
Store this information where it can be displayed when the release details are viewed in the portal (for perf reasons we don't want to load data this every time we load a release, just when we want the single release's details).
Also surface the information so it can be emitted into the build logs when being called through octo.exe
Workarounds
None
Links
https://secure.helpscout.net/conversation/928982696/48679/
https://secure.helpscout.net/conversation/947183334/49665
https://secure.helpscout.net/conversation/958022870/50289
https://secure.helpscout.net/conversation/863730064/45270
https://secure.helpscout.net/conversation/1028513796/54323?folderId=3209064
Prerequisites
The enhancement
What is the problem this solves or benefit it gives
At the moment release creation is a black box, especially the processing and attachment of build information (package metadata). This means that if work items aren't parsed, confirmed and attached there is no explanation as to why not.
Proposed solution
Update the release creation so the issue tracker extensions can return information about the work item Ids they parsed out of the commits and which of those did/didn't exist in issue tracker (e.g. Jira, GitHub, or ADO).
Store this information where it can be displayed when the release details are viewed in the portal (for perf reasons we don't want to load data this every time we load a release, just when we want the single release's details).
Also surface the information so it can be emitted into the build logs when being called through octo.exe
Workarounds
None
Links
https://secure.helpscout.net/conversation/928982696/48679/
https://secure.helpscout.net/conversation/947183334/49665
https://secure.helpscout.net/conversation/958022870/50289
https://secure.helpscout.net/conversation/863730064/45270
https://secure.helpscout.net/conversation/1028513796/54323?folderId=3209064