Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Trending count of issues in a certain status over the course of a sprint or release

I am looking to build a dashboard that shows what status (Testing) of tickets each day is in during a long release cycle.  

So I have 50 stories that I intend for a deployment and the build time to production is 4 weeks.  I want to know how many made it to testing on day 1 how many were in testing day 2 and then the wrong tally day over day.

Day 1: 5 in testing

Day 2: 7 in testing (were in that state during that day, and can move out)

Day 3: 5 in testing


Day 27: 40 in testing


Criteria of what I am attempting to build:

  1. work without caring about the release date for a deployment so I do not have to maintain for various releases.  Looking Rich Text Filter is possible.
  2. Take in the fixversion scheduled release date as my means of subtracting days
  3. Shows day over day in a single gadget
  4. easy to maintain

Initial Efforts on gnarly JQL (does not work presently in current form):

project = PROJECT and status was in (Testing) ON (fixversion in releasedate("on endOfWeek(-2d)")

{and fixversion = 2103.06.00} -- trying to add this via rich text


Want to avoid Custom fields where I have FixVersionX - 1 day

status was in (Testing) ON ("2101-03-01") 

status was in (Testing) ON ("2101-03-02")




1 answer

1 accepted

0 votes
Answer accepted

Hi @Brian Swackhamer   -- Welcome to the Atlassian Community!

What would you do with those specific counts if you had them?  Would having the values as a graphic over time work for your need?

If so, please consider if Jira's version of the Cumulative Flow Diagram (CFD) report would work.  You may adjust to just show the timeframe and status values you care about, and add quick filters for more refinement.

Best regards,



Thank you for the quick response but the CFD is not what I need for this task but the issue I am trying to bubble up is part of the CFD as we have too much WIP on our teams.  What I was tasked with was showing how many issues were actively in the Testing status each day so it can rise and fall as things move to the next status.

What I am attempting to show:

Day 1 of a sprint 4 items are turned over into a testing status.  Day 2 we got two more items but 2 others progressed during the previous day to the next step in the flow towards production so I have 4 items in Testing.  I only care about how many tickets were in that status during that day not overly granular of end of day on Day 1 we had two remaining. 

This is essentially to illustrate an issue that CFD is not providing and the way we have our project currently setup it is not adding the value it needs to.  We are working to clean that up but there is a lot of back and forth that is making the process slow.

Thanks for clarifying, Brian.

Yup, the version of a "CFD" in Jira is missing many assumptions and features of a CFD, including measures at a point in time (and not continuous).  Yet another reason we need a generic built-in Jira gadget to "show me any field or log value over time with basic statistic measures".  Until then, you could...

  • Investigate marketplace add-ons, or
  • Use some custom fields, automation rules, and a spreadsheet to get this:
    • Add a couple of custom fields: EnteredTestingStatus and ExitedTestingStatus
    • Add a scheduled automation rule to set these once per day
    • Regularly export from your project
    • Build a spreadsheet which examines these to determine how many things were in testing status on a given day

convinced my consumers that CFD was the best option.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you