Skip to main content
Skip table of contents

Generating a Status Count Report with the Pivot Table

๐Ÿ“ Context: Tracking the number of times an issue has been in specific statuses is crucial for understanding workflow efficiency and identifying bottlenecks. By using the Time in Status app, you can analyze this data to gain insights into your team's performance.

๐Ÿค” User Problem: Teams need a way to track the number of times an issue has been in specific statuses to understand workflow efficiency, identify bottlenecks, and make data-driven decisions.

Follow these steps:

  1. Open the Time in Status app.

  2. Select a Pivot Table view.

image-20240828-083657.png

3. Then click the Fields button.

image-20240828-084524.png

In the Field menu, you can customize data presentation by setting your custom fields for Rows, Columns, Values.

4. To get the time and story points, drag and drop such fields:

  • Issue Key and Status โ†’ Rows

  • Time (hours) โ†’ Values 

  • Assignee โ†’ Columns 

Choose the Count option in the Values.

5. โ€œCount of timeโ€ (hours) field shows a quantitative indicator (how many times), so set the appropriate format.

  1. For further analysis, export the pivot table to Excel.

As a result, youโ€™ll get the number of times an issue has been in every status for each assignee.

image-20240828-100456.png

๐Ÿ“ˆ Outcomes:

  • Detailed Analysis: Get a detailed breakdown of the number of times an issue has been in each status.

  • Identify Bottlenecks: Quickly identify statuses where issues are frequently stuck.

  • Data-Driven Decisions: Use the insights to optimize workflows and resource allocation.

  • Customizable Reports: Tailor reports to specific needs by selecting different fields for rows, columns, and values.

  • Exportable Data: Export customized reports to Excel for further analysis and sharing.

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.