Work Items can be manually associated on the Build Request Form for each project, or work items can be derived based on commit logs.
Associating Work Items Manually on a Build Request
FlexDeploy ITS Work Items are added to the Build Request using just their number.
Other Work Items are associated using their pattern such as GLORY- + their id. This looks the same as GitHub, GitLab, Jira, etc.
Multiple Work Items can be added using a comma.
Once a build is submitted, the build workflow will attach the tickets entered in the above Related Tickets field to the request. You can see the description and link to tickets in the build and deploy rows and in the Work Items section by clicking the Execution Id link.
Associating Work Items to builds using commit messages in the Change Logs
Work Items are also associated to a build from the source control change logs during a build for each project. The change logs are parsed based on the Ticket Pattern provided in the Project configuration or Issue Tracking System setup page. You can define a single pattern or multiple patterns separated by comma.
In the below pictures, GLORY- is the pattern setup for the project.
To associate a work-item from the FlexDeploy ITS, use the pound/hash symbol like #701 to associate ticket 701.
For Issue Tracking Systems which doesn't support prefix or pattern, you can add your custom parsing rule to extract the ticket numbers from change logs. For this, you can define the pattern inside your implementation class (parseTicketNumberFromChangeLogs is the method which should handle any additional patterns needed by project) and do the parsing accordingly.
The build request parsed patterns like FD-, ZZZ- and Test- from the change logs. This was done inside the parseTicketNumberFromChangeLogs method within the custom Groovy script implementation.