-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
1
-
Currently when we create a branch for the ticket, create a commit with the ticket name in the commit message. Create a pull request in Azure DevOps in which a build is executed. This is correctly displayed in the ticket.
After the branch and thus also the aforementioned commit has been merged into the main branch (and the branch has been deleted), all further builds on the main are also displayed in the ticket, even if the branch has already been removed.
It will better if we only consider the new commits jira issue keys for the build rather than linking historical commit's issue keys which are already linked to some other builds from previous merge. Similar to how it works with Github workflows.