--- title: "Reports" canonical: "https://support.55degrees.se/space/SPI/3975577758/Reports" format: markdown --- Atlassian doesn't make workflow usage data and timestamps easily accessible, so you can't create many of the reports you require to gain the insight you need. Inspekts raw workflow data report fills this gap. In addition to seeing this information in Jira, you can download this data and import it into your reporting tool of choice and create reports to meet your specific needs. # How to read the reports? Below you’ll find information on what the chart should show and how to configure it. ### Duration Report For every issue in a filter, this report shows the total and/or average time it spent in each status. ![Inspekt-Duration.png](media://e09382bf-8a1b-4f5f-95a9-903cb1e5f768) ### Status Timestamp Report For every issue in a filter, this report shows the timestamp for when it first entered and/or last entered each status. ![Inspekt-Timestamp.png](media://b8ae72b2-00a8-45de-a1e5-4962040300e5) ### Status Frequency Report For every issue in a filter, this report shows the number of times an issue was in each status. ![Inspekt-Frequency.png](media://c1a1793b-89d2-42b4-a31e-2e0b7abf76d8) ### Assignee Report This report gives you information about each issue’s assignee history. ![Inspekt-Assignee.png](media://0ce13fea-0e1c-4449-93fb-3bba5107e926) ### Workflow Usage Report This report pulls information from the history of each issue. We gather the data from all of the issues and show the cumulative movement in this report. The interactive chart at the top is called a Sankey diagram. It gives you a visual picture of where work goes when it leaves a workflow state and how often it went there. One workflow state is highlighted upon loading. When you click on a status on the left, the chart updates to show bands indicating how many times an issue went to a particular state on the right. The table at the bottom gives you a text-based view of the same information. If an issue revisits workflow states multiple times, that movement will be reflected in this data. So, you can see the backward movement as well as forward movement of issues through your workflow. ![Inspekt-WorkflowUsageREport.png](media://8723d392-b359-4a4f-a205-a01e85d4a498) **How to use the report?** Often we set up a workflow with a particular process in mind. Though workflows can be configured to force you through that process, often we prefer to have a little flexibility. This report gives you the ability to have that flexibility yet still keep an eye on how the workflow is used. You will learn if certain statuses aren't used as expected or at all. Understanding how the actual workflow differs from the perceived workflow is key for retrospectives. Your board should always reflect reality and current process. If this isn't the case, you could be missing out on seeing opportunities for improvement. **Scenario 1:** If work moves directly from "Workflow step A" to "Workflow step C", you might have a conversation to find out why "Workflow step B" is routinely being skipped. You could discover that more education is needed on the intent of the workflow and why "Workflow step B" is important. Or, you might find out that "Workflow step B" isn't as useful as you thought and it can be removed from your workflow. **Scenario 2:** You notice that work is regularly moving from "Workflow step C" back to "Workflow step B". This could indicate a problem with work quality that needs to be addressed. It could also indicate that "Workflow step B" and "Workflow step C" are part of a cyclical process in your overall workflow. In that case, you might decide to leave it as is or change your workflow to have a single status that represents that overall cycle. This report is all about giving you information on what's going on so you can learn more about how work is really done and what you can do to improve for the future. ### Flow Efficiency Report Are you looking for a way to speed up your work? Removing unnecessary wait time can be more impactful than trying to do your work faster. The total duration of a piece of work can be broken down into 2 components: time spent Working vs. time spent Waiting. The flow efficiency metric portrays this information in a ratio (percentage). A value of 19% means that an item spent 19% of its lifetime actively being worked on and 81% in waiting states. In such situations, focusing on removing waiting time is more impactful than improving the speed of the working time. Once you establish a baseline flow efficiency, you can use this metric to show how much you improve your team's ability to move work through the system with as little waiting as possible. ![Inspekt-FlowqEfficiency.png](media://f18b4d78-4465-4802-a03e-16279f24fde5) At the top of the report, you'll find an introduction to flow efficiency and broken down below by issue type. The entries that show up are based on your issue type and priority configurations. This report shows the past 90 days of the project. It is updated once a day. # How to configure the reports? To configure the reports, click the cogwheel icon in the top right corner of the app: ![Inspekt-Configurebutton.png](media://5ebfcfb3-81f7-4a04-9c06-3a57b6c5a54a) On each individual report, you can then: # How to refine the date range To refine the date range you’re viewing, click ‘Filter by date’ (the calendar icon) in the top right corner of the app. ![Inspekt-FilterbyDatebutton.png](media://be7af40a-2a12-4757-a7c2-f9bed7eabe08) Use the options presented to choose the date range you desire and click ‘Update’. ![Inspekt-Daterangepopup.png](media://96233354-5293-43dd-b6ce-81557795a2f2) # How to export your data To export the data as a CSV, click ‘CSV’ (the download icon) in the top right corner of the app. Any changes such as fields, column order or issue order will be shown as configured in the export as well! ![Inspekt-ExportCSV.png](media://320920a2-2ebb-4a5d-8768-e4bdc7c6cd31) # On your Jira issue 1. Go to any of your Jira issues 2. Click on Inspekt: ![Inspekt-OnjiraIssue-full.png](media://2860efb7-7244-4dd6-922c-c605247a323f) ## How to read the table? #### Cumulative Time Displays the cumulative time the issue spent in each workflow stages. #### First Entered Displays the first time the issue entered each workflow stage. #### Last Entered Displays the last time the issue entered each workflow stage. #### Frequency Displays how often the issue entered each workflow stage. > ℹ️ Why is this important? > ℹ️ > ℹ️ If an issue keeps moving back and forth between different workflow stages, it might be a signal that there is something wrong with it; ie. too big, not well refined,… and a bigger discussion needs to happen with the team to solve it. #### All Assignees Displays the avatar of all assignees the issue has had. Inspekt will show either the avatar or the initials of the users based on their Jira settings. ![image](media://0ae551a9-011d-48da-8682-046e5e07ecae)