How to Set Up and Read Data with Time Reporting Period (Trimmed Data)
- Yuliia Borivets
- Iryna Komarnitska
- Mariana Pryshlyak (Unlicensed)
- Yuliia Shcherbyna
π Context: When generating reports using the Time in Status add-on, you might encounter situations where many line items display nothing in the "Time in Status" column other than βββ. This guide explains what this means and how to address it. |
|---|
π€ User Problem: Users see βββ in the "Time in Status" column for many line items in their report, even though the actual Jira ticket shows an actual Time in Status for "In Progress". They need to understand why this happens and how to fix it. |
|---|
Case: Youβve got a report where many line items display nothing in the βTime in Statusβ column other than βββ.Β When you go to the actual Jira ticket and open the tab, it does reflect an actual Time in Status for βIn Progressβ.Β What does it mean?
Β
Β
Explanation:
Statuses without values don't come under the selected time period. The task was in these statuses either earlier or later than the time range you had chosen in the Time reporting (trimmed) calendar, so they weren't counted.
The data is not trimmed on the issue panel view. So, time is calculated for all statuses for the entire period of the issue's existence.
If youβd like to get time in status data on the add-onβs grid β choose the βAny datesβ option in the Time ranges.
Time in Status add-on offers you two options (calenders) to set report ranges.
Issues period β to choose dates and get a list of issues that have been created/updated/resolved during the chosen period.
Time reporting period β to select the required date range and cut away dates before and after the chosen period.
Read more in the Setting Issue and Time Ranges in Jira Time in Status app section.
π Outcomes:
|
|---|
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!