You can integrate your project with your hosted or local JIRA instances that are externally accessible. This integration works with Jira versions 5.0 and above. Select JIRA from the dropdown on your project’s Integrations page, and enter the following information:
This is the username of a JIRA user who has read/write access to your JIRA instance, via the JIRA API. We recommend creating a user specifically for this integration.
Enter the password of the JIRA user.
For this integration, Tracker uses a saved JIRA filter to choose which issues to show in the JIRA Import panel. You can save a search in JIRA as a filter, and filters appear on your JIRA dashboard. Grab the ID out of the filter URL, which you can see in your browser by hovering over the filter link. Look for requestId=10000 in the URL.
This is the URL of your JIRA instance (e.g., http://yourcompany.atlassian.net).
Update JIRA to allow Tracker Integration by doing the following:
Create a new user with username “tracker_integration.”
Create a new group called “tracker_integration” and add a “tracker_integration” user.
Grant the following permissions to the new “tracker_integration” group or user: Edit Issues, Assign Issues, and Close Issues.
Create a copy of the default workflow in JIRA, with additional conditions on each transition to allow users in a designated Tracker integration group to complete that transition, as described in the JIRA docs. To do this, edit the Transitions and add the tracker integration group as an “OR” condition for the following Transitions: Open > Start Progress, In Progress > Stop Progress, Resolved > Reopen Issue, Reopened > Start Progress, Closed > Reopen Issue.
On the Project Admin page, change the Workflow Scheme to the new scheme.
How the integration works
Stories created from JIRA issues will be linked to the corresponding issue, and you will see a link to the JIRA issue on the story. Any comments added to the story will appear as comments in the JIRA issue. Also, as the Tracker story is started, finished, and accepted, the state of the linked JIRA issue will also update accordingly (unless Update Comments? or Update State is unchecked on the configuration page). For instance, when the state of the Tracker story changes to Started, the associated JIRA issue will change to In-Progress. Likewise, Tracker’s Finished state maps to Resolved in Jira; Accepted maps to Closed and finally, if the story is Rejected the JIRA issue should change to Re-Opened. So only the Tracker states of ‘Started’, ‘Finished’, ‘Accepted’ and ‘Rejected’ will cause the JIRA issue to change state (the Delivered state causes no changes).
Currently, only the default JIRA issue workflow is supported. If you’ve configured your JIRA instance with a nonstandard workflow, issue state updates from Tracker may not work. Also, you may need to enable API access for your JIRA instance in Administration/General Configuration (select the Accept Remote API Calls option).