Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How does control chart calculate time in status if an issue happens to be twice in the same status? Edited

As per title, imagine a workflow where an issue could be more than once in a status:

To Do -> Development -> Testing -> Development -> Testing -> Done

 

Does time spent in Testing is:

  • calculated in total for both "instances" of testing
  • calculated separately for each instance of testing
  • calculated only for last instance of testing

 

1 answer

Hi @Michał Kwieciński 

"Control chart - shows the Cycle Time (or Lead Time) for your product, version, or sprint. It takes the time spent by each issue in a particular status (or statuses), and maps it over a specified period of time. The average, rolling average, and standard deviation for this data are shown."

You can read more here https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

Additionally, you can consider Time in status for Jira cloud or Time Between Statuses apps from the Atlassian marketplace if you want to get more detailed information about the status durations.

The first one automatically calculates the time each issue was in each status. Second add-on lets you set start and stop statuses for timer and add such condition as first/last transition to/from status. 

Hope it helps

Regards

Thanks for the tips.

With regard to the core of your answer, I think the explanation is vague enough for me to still have doubts how it is actually computed. The questions remains open :). 

Daniel Ebers Community Leader Jan 27, 2021

Testing in cloud instance I can recognize it is calculated for a specific status in total (a simple addition of time spent, no matter how often the issue was in a particular state).

Like Michał Kwieciński likes this

Thank you, if it is empirically confirmed, I would very much like to accept your answer :) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,121 views 8 28
Join discussion

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