Timepiece—Time in Status for Jira now introduces improved support for the Sprint field in Any Field Duration reports. With Timepiece, it is now possible to report the time each issue spent in each sprint.
For newbies in this subject, this is the second step of improving Timepiece’s support for the Sprint field following the recent introduction of Sprint (Current) and Sprint (Latest) fields.
First, a quick reminder
As you know, a Jira issue can take part in multiple Sprints and Jira keeps the names of those Sprints in a custom field named Sprint. This field is a multi-value field and it keeps the names of all Sprints the issue was assigned to (if the issue was in the Sprint when the Sprint was completed). If the issue was removed earlier, the Sprint change stays in the issue history but its name is not kept in the Sprint field. Conversely, if the issue was completed in the Sprint and it was still in the Sprint when the Sprint was completed, there will be no change in the issue’s history but the Sprint field will start displaying an empty value (it will show the sprint name as an ol value when you click the plus sign).
All of this complexity makes it very hard to see the time an issue has spent in each sprint (or the backlog). The usual workings of Any Field Duration report can’t handle these because of all the reasons explained above.
We decided to dive into this problem head first and successfully built a solution for it.
Timepiece to the rescue
With this new solution, the Sprint field gets special treatment when selected as a History Field in an Any Field Duration report. For the Sprint field, Timepiece will make calculations considering both the issue history and the Sprint history of the system and create a report showing how much time each issue spent in each sprint or the backlog.
It doesn’t matter if the issue was created in the sprint, added after the sprint started, completed in the sprint, or removed before the sprint was completed. In all cases, Timepiece will show the time spent in each sprint.
How do I use it?
For the end user, the experience is exactly the same as any other Any Field Duration report. The user switches to Any Field Duration report and selects Sprint as the History Field. Timepiece will take care of the rest.
Where can I find it?
Improved handling of Sprint field in Any Field Duration reports are available on Timepiece for Jira Cloud. and were introduced to Timepiece for Jira Data Center starting with v5.3.0.
Conclusion
The improved accuracy of the Sprint field in Any Field reports, combined with new Sprint fields will give you great power and flexibility in Timepiece reporting.
To learn more about Timepiece – Time in Status for Jira, you can visit its product website or Atlassian Marketplace page.
If you have further questions, you can reach the OBSS support team through appsupport.obss.tech or by sending an e-mail to appsupport@obss.tech
