Skip to main content
Skip table of contents

Calculating Time in Status for Linked Issues Across Multiple Projects

πŸ“ Context: Managing interrelated tasks across multiple Jira Service Management (JSM) projects can be complex, especially when the status change of a task in one project requires a corresponding status change in a linked task in another project. While Jira's built-in functions do not support displaying this information directly, you can generate the desired report using the pivot table view. This guide explains how to create a tailored report detailing the time spent in status for linked tasks across various JSM projects.

πŸ€” User Problem: Teams need a way to track the time spent in status for interrelated tasks across multiple JSM projects to gain insights into the efficiency and efficacy of support and service resolution workflows.

In the given context, involving multiple JSM projects and dependencies on linked issues with distinct workflows, computing the time spent in status or duration offered significant insights into the efficiency and efficacy of support and service resolution workflows.

Following a straightforward process and employing a JQL query, users can generate a tailored report detailing the time spent in status for linked tasks across various JSM projects.

image-20240821-073829.png
image-20240821-073839.png

πŸ“ˆ Outcomes:

  • Measure End-to-End Resolution Duration: Understand the total time taken to resolve interrelated tasks.

  • Evaluate Resolution Time for Supporting Issues: Identify how long it takes to resolve linked tasks.

  • Comprehensive Time Evaluation: Gain a holistic view of the time spent on interrelated tasks.

  • Issue-Specific Performance Metrics: Analyze the performance of individual issues and their linked tasks.

If you need help or want to ask questions, please contact SaaSJet Support or email us at support@saasjet.atlassian.net

Haven't used this add-on yet? Try it now

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.