Connect Jira with all of your tools to help scale DevOps
Jira is by far the most popular Agile tool in the software delivery toolchain today. It plays a central role in planning and tracking work, primarily for engineers, but often for other teams as well. Integrating Jira with other application development and delivery tools keeps teams and tools in sync automatically, so you can focus on the real value-adding work of developing new features, resolving defects, closing tech debt, and reducing risk.
Common artifacts flowing in integrations include: Story, Bug, Issue, Epic, Sub-task, Custom Issue, and Custom Sub-task.
Why Integrate Jira?
Integrating Jira with other tools ensures engineers can spend their time on doing the work that creates value for the business, instead of the busy work required to keep tools and colleagues in sync.
A good integration means:
- You don’t need to enter the same information in multiple tools! Any update you make in Jira automatically flows to the right place in other tools and vice versa
- You don’t need to login to multiple tools to do your work. All the information you need is right there in Jira, including all the fields, descriptions, attachments, and comments changed in other tools
- You don’t need to communicate about an issue in chats, emails or status meetings! All communication can take place and be seen within Jira comments, even when colleagues enter their replies in other tools
Integration can also tie together multiple Jira instances, even if they are at different version levels, and have them working as one. The same is true for coordinating work between on-prem instances and on-demand instances running in parallel and supporting migration between the two.
To see everything Jira integrates with through Tasktop, visit our full list of tools.
Most Popular Jira Integration Patterns
While there are many use cases for integrating Jira, below are the top five most popular integration patterns in 2018.
#1 Test Management to Jira: Improve Defect Resolution
Integrating test management tools such as Micro Focus ALM (HP ALM), Tosca, or QASymphony with Jira improves alignment between software engineers and test engineers. Defects opened in test management are automatically created in Jira as new issues in the appropriate project’s board. Changes made to the defects’ status in Jira are visible to the QA engineer in test management.
Here’s an example of this pattern in Tosca and Jira:
#2 Jira to Test Management: Improve Product Quality
One of the most effective ways to improve product quality is to improve the quality and scope of tests. This integration pattern involves QA engineers into the process early on, by flowing Jira stories to test management tools, like Tosca, ALM and QAComplete. QA engineers and test automation engineers can easily communicate with software engineers about the story, each from within their own tool.
#3 Jira to Agile Issues & Tracking: Improve Performance Management
It is not uncommon for an organization to have multiple Agile issues and tracking tools, with some teams or roles using Jira and others using another tool, like VersionOne, Targetprocess or LeanKit.
This integration pattern creates one master view of the activity across all Agile tools, by flowing the epics, stories, bugs, sub-tasks and other artifacts into one of the tools as ‘master’. Reports are run off the master, encompassing data from all Agile tools.
#4 Requirements to Jira: Improve Traceability and Product Quality
Product owners and business analysts gather, articulate and prioritize requirements in requirements management tools, like Jama, Targetprocess and DOORS NG. Engineering leads may often feel like "Product's Secretary", forever manually updating the Jira epic with all the decisions, requirements and acceptance criteria that are discussed with Product.
This integration pattern eliminates that hassle. It flows requirements into Jira as epics and user stories, creating a traceable link between the requirement and its implementation. A contiuous synchronization keeps artifacts in both repositories perfectly aligned, even as information is added, questions are raised and answered, and work progresses to completion.
Here’s an example of this pattern between IBM DOORS Next Gen and Jira:
#5 ITSM to Jira to Test Management: Improve Ticket Resolution
This integration creates a visible and traceable defect reporting and resolution process. Trouble tickets opened in an ITSM tool like ServiceNow or Remedy are automatically created in Jira as new issue or story. When it’s ready for test, the issue flows to test management. When the issue is indeed fixed, it closes in Jira and ITSM is updated. The support engineer in ITSM has visibility on the status of the ticket resolution at all times.
Here’s an example of this pattern in ServiceNow, Jira and Micro Focus ALM:
Discover more Jira integration patterns.
Tasktop runs over half a million tests a day in our Integration Factory to ensure integrations work across all our supported endpoints even as new tool versions are released and APIs change. Through continuous testing, Integration Factory allows us to support over 300 endpoint versions and seamlessly handle complex artifacts and their relationships, as well as respect the customizations, workflows, permissions and other aspects of the endpoint tools, without the need for any coding or professional services.
Check out the list of Jira versions we support.
Jira Integration Plugins vs. Tool Integration Infrastructure
Many tools offer integration plugins for Jira. While plugins are easy to install and require minimal configuration, they also have many serious limitations, which make them unsuitable for large software delivery organizations with hundreds or thousands of projects. Enterprise IT requires the nuanced integration capabilities of proper integration infrastructure.
Consider these common problems with plugins:
- The plugin adds functionality to Jira universally, meaning that new field or button appears for all projects or all artifact types. Everyone sees it whether they need it or not.
- The plugin adds functionality to one single project. If you need the functionality for hundreds or thousands of projects, you need to install it hundreds and thousands of times.
- The plugin creates an issue - which is what you want - but it doesn't allow you to update all the fields you need.
Tasktop Integration Hub has none of these limitations. It requires no installation on the Jira server. Admins have complete flexibility to select the projects and issue types to integrate. They also have total control over which fields to display and how they will be updated.
Toolchain Integration Best Practices
Debating whether to build your own Jira integrations? Read our insights from experiments connecting two, and then three, application development and delivery tools.
Wondering whether now is the right time to begin your integration? Check out our infographic on the top 6 reasons not to delay.