Creating an OAuth Token for FlexDeploy ITS
Go to Jira and login as the user you want to comment on Jira Issues with.
Generate an API Token in Jira following this guide.
Jira ITS Instances
A Jira instance looks like this:
Setting Up Folders and Projects to Use the Jira ITS Instance
Then back in FlexDeploy, set up your folder ITS settings like this:
Linking Jira Issues to FlexDeploy Builds
Now you are ready to link tickets with commits or by manually entering them on project builds or project packages.
Linking with Commit Messages
Set up your FlexDeploy Project with a ticket pattern. The pattern must be Jira Project name + “-” + issue number.
Following this pattern, make a commit message.
Push and merge your change.
When you create a build, the issue numbers are pulled from your commits.
Linking by Manual Entry at Project Build Time
If you didn’t remember to put the issue number in your commit, and you are building the project manually, you can enter issue numbers at build time.
The issue number should be Jira Project Name-Issue Number
In this example, it’s FLEXDEPLOY.
Linking 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.