Since FlexDeploy 7.0.0.3, all All FlexDeploy Jira integrations now support v3 of the Jira REST API. Users who opt into v3 will notice more accurate comments and descriptions when viewing Jira Work Items in FlexDeploy. You can begin utilizing v3 by updating the Jira REST API Pattern property on your Jira Integrations (e.g. /rest/api/3/issue/{JIRA_ISSUE}).
...
A JIRA instance looks like this:
Property Name | Property Code | Required | Description |
|---|---|---|---|
Jira URL |
| Yes | Jira URL (For example http://myjira.atlassian.net) |
Jira User |
| Yes | Jira User Name |
Jira API Token |
| Yes | Jira API Token. See (https://confluence.atlassian.com/cloud/api-tokens-938839638.html) to learn more about API tokens and how to create them. |
Jira Ticket URL Pattern |
| Yes | Jira Ticket URL Pattern (/browse/{JIRA_ISSUE}) |
Jira Rest API Pattern |
| Yes | Jira Rest API Pattern (/rest/api/2/issue/{JIRA_ISSUE}) |
...
Configure Folder or Project for Issue Tracking
...
using commit messages - use the format #issue for example, #GLORY-1234. Or you use GLORY-1234 in commit message if GLORY- is setup as work item pattern. You can use one or more issue numbers in commit message, but it is good idea to have separate commits for each issue.
manually at build time - just specify issue number(s) on build request form in work items input. For example, GLORY-1. Note that # prefix only necessary with commit message.
manually with package - just specify issue number(s) on package configuration.
See Link Associate Work Items to Project a Build for more information about linking Work Items to builds.
...