Introducing New Sprint Fields for Timepiece (formerly Time in Status) Reports


We have good news for those who want to use Jira’s Sprint fields in Time in Status reports of Timepiece.

What was the problem?

Jira issues have a custom field for Sprint information but this field keeps the Sprint data in a funny way. This field keeps the names of all the current and past Sprints that the issue was part of.

This had a direct impact on Timepiece reports when you wanted to get a “time in status” report. When added as a column to the report, this field displays all the sprint names (not bad, still kinda useful). When selected as a Group By field for an aggregate report, this field still displays all the sprint names, making the grouping totally useless.

What is the solution?

With this week’s release, Timepiece (formerly Time in Status) is introducing two new fields. Sprint (Current) and Sprint (Latest).

As the name suggests, The Sprint (Current) field displays the name of the current sprint.

The Sprint (Latest) field, on the other hand, displays the name of the latest sprint that the issue was part of.

You can use these fields for both Fields selection and Group By Fields selection.

Sprint fields added as columns to a Timepiece list report
A Timepiece Average report with Sprint (Latest) field selected as a Group By field.

To learn more about Timepiece (formerly Time in Status), you can visit its product website or Atlassian Marketplace page.

If you have further questions, you can reach the OBSS support team through pluginsupport.obss.com.tr or by sending an e-mail to plugin@obss.tech