Want to link a Jira issue with a requirements document in Confluence, or with a support ticket in Desk.com, or even with a Google search result you found? With Issue Links in Jira 5 you can quickly and easily append important information to your Jira issues to give you more context, facilitate collaboration, and help you build better software.
Whether you are adding a test cases from Zephyr, a discussion topic from Get Satisfaction, or a customer record from Salesforce, Issue Links puts all of this and more at your fingertips.
Linking from Jira
Let’s start with basic issue linking from within Jira. Issues in Jira can be linked within the same Jira instance using bi-directly relationships.
For example, maybe we’re working on a set of mockups and are tracking their progress in Jira. We might have one Jira issue for the banner image and separate Jira issues for each of the copy blocks. By linking these issues together, as requirements of each other, we can quickly keep track of their details and status from one location within Jira.
In our case above, the master landing page “has requirements” for each of the 3 child pages. In turn, those child pages are “requirements of” the 1 master landing page. With issue links in Jira, all of this information is easy to organize.
Remote Issue Links
With Jira 5, you can now link to issues in a remote Jira instance or pages in Confluence.
The project lead wants to link the landing page work mentioned above to some development tasks in a separate instance of Jira. All we have to do is configure application links and our remote Jira instance will now show up in the Server list in the Link dialogue box. From here issue linking works exactly the same as is outlined above (in this case bi-directional or reciprocal links are optional).
Linking a Jira issue to a Confluence page is incredibly easy. We can use the same dialogue box shown above to add a link or search for our desired page in Confluence and add it to our Jira issue.
Linking to Jira
External applications can link to Jira issues remotely to add important visibility into your development process and shorten the time it takes to locate associated records in your external systems.
For example, paste a Jira issue URL directly into a page in Confluence 4.1 to automatically create a link between the two.
But what if you want to link a remote application to Jira? With Jira 5 we extended issue linking to allow any add-on to easily add an issue link to Jira using our Java or REST APIs. This is great for you to keep track of a Jira issue that came from a case in Salesforce, a ticket in Zendesk, or an error in New Relic. Now you can see exactly where your issues came from, and what they relate to outside of Jira.
Compatible Add-Ons
The following integrations and plugins are fully functional with Jira 5 remote issue links today:
Box
Desk.com
Enterprise Tester
Get Satisfaction
Connect your Get Satisfaction community to Jira and let your customers incorporate feedback directly into the product development process.
Google Docs
HockeyApp
IBM Connections
Innotas
JaM
Jama Contour
Jive
New Relic
Salesforce.com
Provides connectivity between Jira and Salesforce.com to create, update, and manage both Jira issues and Salesforce cases.
Sauce Labs
The Jira – Scout plugin enables Jira users conducting exploratory testing using any of the 35+ browsers in the Sauce Labs cloud to attach video, screenshot and narrative artifacts of those tests to new or existing Jira incidents.
synapseRT
U-Test
With the uTest Jira plugin, you can close the loop between uTest and your engineering teams.
UserVoice
Zendesk
Zephyr Enterprise
