{"id":20888,"date":"2020-02-18T09:28:14","date_gmt":"2020-02-18T15:28:14","guid":{"rendered":"https:\/\/blog.planview.com\/jira-integration-use-cases\/"},"modified":"2020-02-18T09:28:14","modified_gmt":"2020-02-18T15:28:14","slug":"jira-integration-use-cases","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/jira-integration-use-cases\/","title":{"rendered":"The Top 6 Jira Integration Use Cases"},"content":{"rendered":"
\n
\"The<\/div>\n<\/figure>\n

As a platform for helping development teams to plan, track, and release software, it’s no wonder that Jira is such a popular Agile Planning tool in the software delivery toolchain today. But if you’re part of a large and complex organization, Jira probably isn’t the only tool you’re using to plan, build and deliver software at scale.<\/span><\/p>\n

The use of multiple, non-integrated tools creates a fragmented workflow, constraining efficiency and data integrity across the software delivery value stream — and across the rest of your business. That’s why thousands of global enterprises know it’s critical to integrate Jira to overcome these challenges.  <\/span><\/p>\n

Through our work with the Fortune 100, we have identified six popular use cases for integrating Jira with other best-of-breed tools used to plan, build and deliver software at scale. <\/span><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n

  • But First, Why Integrate Jira? <\/a><\/li>
  • The Top 6 Jira Integration Patterns<\/a><\/li>
  • Learn More About How to Integrate Jira Using Tasktop <\/a><\/li><\/ul><\/nav><\/div>\n

    <\/span>But First, Why Integrate Jira? <\/strong><\/span><\/h2>\n

    When you integrate Jira with other tools, you allow your developers to spend more of their time on doing the work that creates value for the business, and less on time-intensive work required to keep tools and colleagues in sync. We’ve estimated that on average, integration and automated data flow can save each practitioner (developer, tester, project manager, ITSM etc.) up to 20 minutes per day on tedious manual overhead — that works out at a whopping ten working days a year.<\/span><\/p>\n

    <\/p>\n

    High quality, enterprise-scale integration means:<\/span><\/p>\n

      \n
    • 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.<\/span><\/li>\n
    • 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.<\/span><\/li>\n
    • 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. <\/span><\/li>\n
    • You can seamlessly collaborate across multiple Jira instances and versions, like on-prem and cloud instances.   <\/span><\/li>\n<\/ul>\n

      <\/span>The Top 6 Jira Integration Patterns<\/strong><\/span><\/h2>\n

      While there are many use cases for integrating Jira<\/a>, below are the top six most popular integration patterns <\/span>as collected by Tasktop from an analysis of hundreds of enterprise<\/span><\/a> toolchains.<\/span><\/p>\n

      #1 Test Management to Jira: Improve Defect Resolution<\/strong><\/h4>\n

      Integrating test management tools such as Micro Focus ALM (HP ALM)<\/a>, Tricentis Tosca<\/a>, or QASymphony<\/a> 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.<\/span><\/p>\n

      Here’s an example of this pattern between Tosca and Jira: <\/span><\/p>\n