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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Status impact on metrics in Kanban



My Team is starting with Kanban. I am interested to understand how will status On Hold that is setup in our company with blue color impact on Kanban metrics. When PBI is in this status, it means it is blocked for further Development until blockers are resolved. Thanks!

2 answers

0 votes

Hi @Jovanka Jovicic 

Would you please clarify your status values and Kanban board layout, as those may impact the answer to your question?  In general, the built-in Jira reports/measures are based upon a board's filter and the board's column settings, and the actions of the team.


For some context, teams using Kanban practices often use the following measures:

  1. Lead Time: the calendar time from creation to completion of an item
  2. Cycle Time: the time from one point in your flow to another.  For example, Build Cycle Time could be from the start of work until completion.  This could be measured in calendar or working time.
  3. WIP: the count of items in progress, regardless of any other indications (i.e. blocking)
  4. Age of WIP: the working time an item has been in progress.

Jira out-of-the-box cannot measure Age of WIP, and the other measures can be tampered with by altering the board filter after work completes.


If your "on hold" status is before work starts on the board, there is no impact to your measures.  If instead this is a status mapped to a board column (i.e. your workflow), generally teams using Kanban would include "on hold" time and issue counts in measures.  Otherwise that is both hiding work and dis-incentivizing the team from considering how to resolve/reduce "on hold" occurrences now and in the future.


Kind regards,

Thank you @Bill Sheboy  for your answer. As I understand we just need to keep in mind to exclude this status from calculations. 



Hey @Jovanka Jovicic 

here is a thread where your question is answered - it will tell you how to make sure On Hold does not count into "Worked on" time

Thank you @Marta Woźniak-Semeniuk , but my question is related to the impact of reporting. 

We once used a plugin for this it gave us data for WIP including and excluding the time spend on hold/in blocked status for reporting.

We had to do it with excel but it gave us great insight into our blocking times and it helped us manage the workflow better :) 

It's free so you can just try it out and see if it helps :)

Like Jovanka Jovicic likes this

Suggest an answer

Log in or Sign up to answer