4 Ways Agile Teams Reuse One Time in Status Report

[#1]

A Time in Status report usually gets built for one purpose and one audience. Then 3 other teams ask for "the same thing, but just for us," and you end up cloning the report or editing the dashboard gadget every time someone needs a narrower view.

Quick Filters in Timepiece removes that back-and-forth. The person who builds the report exposes a short list of Jira fields as filters. After that, anyone looking at the report or gadget can pick values, click Apply, and see the numbers recalculated for just their slice. No edit rights on the report or the dashboard are needed. Their choices are appended to the report's query, and the saved report is left untouched.

Here are four situations where that turns one report into many.

1. Give every team its own slice of a shared dashboard

You built one status-time gadget for the whole department, but each team only cares about its own issues. Expose Component (or your team field) as a Quick Filter, and each viewer narrows the same gadget to their work. Nobody clones the gadget, and nobody needs edit access to the dashboard.

When a viewer picks the Checkout component, the gadget's base query effectively becomes:

project = SHOP AND component = "Checkout"

2. Slice a Cycle Time report to the sprint you're reviewing

In a retrospective you rarely want all-time Cycle Time. You want this sprint, and maybe just stories. Offer Sprint and Issue Type as Quick Filters, and you pull the exact cut live in the meeting instead of rebuilding the report first.

project = DEV AND sprint = "Payments Sprint 24" AND issuetype = Story
 

3. Keep a shared report about the flow, not the people

Sometimes a widely shared report should stay focused on the process and not turn into a spotlight on individuals. Offer only fields like Priority and Component, and leave Assignee out of the filter list. Viewers can still drill into what matters, such as high-priority work or a specific component, without the report becoming about who is slow.

project = OPS AND priority in (Highest, High) 

4. Stop being the person who edits everyone's gadget

Every "can you tweak the dashboard for me?" request is an interruption, and it usually means handing out edit rights you would rather not. Quick Filters gives that control to viewers, but only within the fields and options you chose. You build the gadget once, and they adjust the view themselves.

  

The same setup on the page and on dashboards

Quick Filters behave the same way on the main Timepiece reporting page and inside dashboard gadgets. Set the filters up once on the reporting page, save that report, and the gadget you build from it carries the same filters, so you don't configure them twice.

The pattern holds in every case: build the report once, expose a few fields, and let each viewer answer their own version of the question. Quick Filters is available in Timepiece - Time in Status for Jira Cloud on its Atlassian Marketplace page.

[Anwesha Pan]

Thanks @Birkan Yildiz _OBSS_ for sharing this article.

[Birkan Yildiz _OBSS_]

Thanks, @Anwesha Pan . 
Glad you found it useful.