Work Items can be manually associated on the Build Request Form for each project build, or work items can be derived based on commit logs.
| Tip |
|---|
Work Items are linked to build only if they are found to be valid based on Project’s Issue Tracking configurations. |
Associating Work Items Manually on a Build Request Form
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
...
Link by Commit Messages
Work Items are captured and linked to a build from the source control change logs during a build for each project. The change logs are parsed based on the Ticket Work Item Pattern provided in the Project configuration or Issue Tracking System setup pageconfiguration. You can define a single pattern or multiple patterns separated by comma. Issue Tracking configurations are inherited by sub-folder and projects, this is very easy to view and manage on Project Issue Tracking page.
| Tip |
|---|
Easiest option to specify work items in commit message is prefixing by #. There is different in how work item numbers are specified for each type of issue tracking system. See individual integration page for more details. |
In the below pictures, GLORY- is the work item pattern setup for the project.
...
| Info |
|---|
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. |
Link by manual Entry at Project Build Time
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.
...
Link Issues to Project Packages
If you don’t put issue numbers in your commits and you are working with a package-based project, you can associate issues with packages that will live through its build and deployment lifecycle by following this pattern. Go to the project and package which you wish to link a Jira Issue. Edit the package.
Add one or more Issues. The dropdown only shows previously linked issues. Type the entire issue key to make a new one.
...
Save.
The issue number should be in the format Jira Project Name-Issue Number
Now, builds and deployments of this package will be associated to that Jira Issue.