Since QuickBuild 3, a two-way solution is provided to integrate with Atlassian JIRA. The integration features:
- Hyperlink the JIRA keys in commit messages to corresponding JIRA pages
- Generate an issues report from commit messages
- Progress/update the issues from commit messages
- Release a version of a project in JIRA and update the fixed versions field of issues with status fixed or closed
- Create an issue to JIRA based on a customized step condition
- View SCM changes for each issue
- View related builds for each issue
- View related builds for each project
This page will describe how to integrate JIRA in QuickBuild.
On This Page
Supported JIRA version should be JIRA 3.13.3 or higher.
To enable the integration:
1. Enable 'Access remote API calls' in JIRA Administration
2. Configure JIRA server in your configuration setting tab
You can associate a JIRA project with this configuration. This project is used when you want to update issues or release version to JIRA. See details below.
After doing these, the issues keys mentioned in commit messages will be hyperlinked:
and an issues report tab will be displayed in Build tab:
NOTE The issues here will synchronize with JIRA to reflect their latest status.
you can also find all related issues from a specified version and view their changes:
After configured the JIRA server in the configuration settings, below steps are available to add in your build workflow:
- Update Issue Step
- Release Version Step
- Create Issue Step
Besides the basic integration, QuickBuild also features:
- Update issues mentioned in commit messages directly
- Cooperate with JIRA to manage both JIRA and QuickBuild version
- Release a JIRA version and also update the Fix Version/s field of issues mentioned in commit messages which can help you to generate the Release Notes easily.
To update issues from the commit messages, Update JIRA Issue step should be added to your build workflow. And you need specify one or more issue updater(s) below in the step:
- Update issues according to SCM commit messages
- Update issues by a specified JIRA filter
- Update issues with specified issue keys
- Update issues corresponding to changeset closed tasks
By default, QuickBuild will update issues according to SCM commit messages.
When QuickBuild find any commit commands in the commit message, it will execute these commands to update or progress the issues listed in the commands.
- This step should be defined after your checkout step.
- QuickBuild will update all issues which are requested from the commit comments from previous successful build.
- If issue updated manually after committed, this issue will not be updated then.
- Only issues which belong to the associated project be updated.
The commit command has two types:
- Progress Command which is used to progress an issue in the JIRA workflow and step attribute is required.
- Update Command which is used to update an issue only and will not lead to a workflow transition.
The commit commands can be customized in the Update Jira Issue step based on your JIRA workflow definition.
A commit command has below attributes, each attribute relates to the field of an issue:
|summary||a brief one-line summary of the issue.|
|description||a detailed description of the issue.|
|type||the type of the issue, for example: Bug, Improvement, Task, etc.|
|priority||the importance of the issue in relation to other issues.|
|resolution||a record of the issue's resolution, if the issue has been resolved or closed.|
|step||the workflow transition that this command triggers. For example, step=Start Progress will progress issue to 'In Progress' status. See JIRA workflow for details.|
|reporter||the person who entered the issue into the system.|
|assignee||the person to whom the issue is currently assigned.|
|duedate||specify the issue due date.|
|dateFormat||specify the date format for due date.|
|environment||the hardware or software environment to which the issue relates.|
|affectsVersions||project version(s) for which the issue is (or was) manifesting.|
|fixVersions||project version(s) in which the issue was (or will be) fixed.|
|comment||the comment which will be added to the issue and will be diplayed in issue comment tab.|
Records the time tracking information of an issue. The syntax for time is:
Here, <n> is user specified time period. For example: 1w 2d 3h 20m Total cost period - this will record 1 week 2 days 3 hours and 20 minutes against the issue and add the comment 'Total cost period' in the Work Log tab of the issue.
JIRA custom fields are also supported, for custom fields, below format can be used:
here, 10000 is the field id of a custom field, and 'My Custom Field Name' is the name of the custom field. Please reference http://confluence.atlassian.com/display/JIRA/Custom+fields for details about custom field or consult your JIRA administrator for the custom field id.
Below we will give some example commit messages to illustrate the commit commands:
- In below commit message, QuickBuild will resolve the issues TST-1 and TST-2 and add comment The issue has been fixed to both issues.
- In below commit message, QuickBuild will add 2d 3h to the worklog and add comment Some comment to issue TST-1. The value of time 2d 3h should be used the format defined in JIRA time tracking.
- In below commit message, the value of custom field 10000 will be updated to for custom field
You can define common attributes in the Update Jira Issue step so that when updating issues, the attributes can be applied to all of the issues. When an attribute is specified both in commit command and Extra Attributes, the value in commit command will be used.
This updater is used to retrieve the issues to be updated from a specified JIRA filter. This filter should be saved by the user defined in configuration JIRA server setting. And you also need specify the workflow action you want to take.
Unable to render embedded object: File (filter-updater) not found.
This updater is much similar to update issues by filter. You can specify the JIRA keys directly here, or you can input a script here to generate the issue keys to be updated.
Currently, this updater can only work with Perforce. If your Perforce job is associated with JIRA issue, QuickBuild will extract the issue keys from those closed jobs and then update the issue status.
To release version to JIRA, Release JIRA Version step should be added to your build workflow. And this step will release the build version to the associated project in JIRA. If this version does not exist, QuickBuild will create it automatically. Also, you can define one or more issue provider(s) below to provide the issues which you want to update their 'Fix Version/s' fields:
- Resolved/Closed issues found in commit messages
- Resolved/Closed issues in previous update issue steps
- Issues filtered by a specified filter (the filter should be saved by the user defined in configuration JIRA server setting)
- Issues with specified keys
- Issues corresponding to changeset closed tasks (currently, this can only work with Perforce, see Update issues corresponding to changeset closed tasks above)
- Do not update issues
The filter should be saved by the user defined in configuration JIRA server setting.
You can specify the issue keys directly or you can input a script to generate the issue keys.
Currently, this can only work with Perforce. If your Perforce job is associated with JIRA issue, QuickBuild will extract the issue keys from those closed jobs.
If you don't want to update the Fix Version/s field, you can use this.
The version can be managed either from QuickBuild or from JIRA:
By default, the version is managed by QuickBuild, that means you need not define any version for the associated project in JIRA and QuickBuild will automatically create and release the version of this build.
Sometimes, you want to manage the versions in JIRA side by yourself and let QuickBuild retrieve the version from JIRA. In this scenario, you just need change your Next Build Version (in configuration settings -> General Setting section) to use next unreleased version from JIRA, and then you will find the next build version will be the first unreleased version you defined in JIRA when go to configuration dashboard.
You may create an issue from QuickBuild by adding a Create JIRA Issue step. A common case is that when build failed, create an issue so that we can track the build from JIRA.
- Q: I have written the commit commands in my commit message correctly, but QuickBuild doesn't execute them and update the issues.
A: In most cases, that is because your SCM user does not associate with your JIRA account correctly. See how to associate them in this page.
- Q: I can't add comment to a closed issue, why?
A: You need modify the file $JIRA_HOME/atlassian-jira/WEB-INF/classes/jira-workflow.xml, find 'Closed' step and change the value of 'jira.issue.editable' to true.
- Q: The commit command failed with error: Workflow step 'Start Progress' is not valid for issue: ABC-123.
A: Normally, this is caused by several commit commands were submitted in wrong order to change the issue status. For example, two commit commands submitted to progress issue TST-123:
1. Close TST-123 // OK, changed status to Closed
2. Fix TST-123 // Error! Workflow step is not valid
- Q: How to update a custom field with multiple users selection
A: To update a custom field with multiple users, you can input below lines in the Extra Attributes field:
customfield_Your Users Field=name:steve,name:robin
That is, use comma to separate the user and use colon to separate the property.
To trigger build via JIRA webhook, first, you need create a webhook setting in JIRA like below:
Here, the URL is in below format:
Please replace the QuickBuild host and token with your actual value.
The token is used for verification with QuickBuild.
After setting up at JIRA side, go back to QuickBuild, in Administration -> Plugin Management page, search JIRA plugin:
then config it by filling below two fields:
- Project Mappings, config the project mappings between JIRA project and QuickBuild configuration.
- Token, specify the access token for security reason
then, go to the configuration you want and set up the webhook setting in the configuration setting:
filling below fields: