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

Is there a way to update builtin JQL for Sprint Health Gadget to display issues in various statuses?

Sprint Health Gadget displays "To Do" status for 1st column and "Done" for the last column and the rest under "In Progress" status irrespective of actual statuses of Sprint Stories.

As we have "Blocked" as first column, it shows all issues with blocked status in Sprint Health Gadget under status "To Do" and when I view in issue navigator it uses JQL - status ("Blocked") AND Sprint = 110, which is incorrect.

It should show Stories with "To Do" status under "To Do" in Sprint Health Gadget. Is there a way to correct built-in JQL or any other way to display statuses correctly?




1 answer

1 vote
Sudarshan TS Community Leader Apr 09, 2021

Hello @Vinay Sharma 
No! not possible, the 3 states shown by the sprint health gadget is based on the status category (To-do, In progress, Done).

What I suggest is that -- your Jira admin need to change your Blocked status category from "To-do" to "In-Progress" then your JQL will be ok.

Atlassian has decided not to make any changes with this according to  - this is based on Jira server --

Have a look at this market app for new status and colors (its nice :) )

Think deeper as to where your problem is:
If we think deep Blocked is not actually a status in scrum it is a "I dont know how to proceed" or "waiting for that code" situation of your development activity (its not a like a lifecycle), do you really need a status to say what is blocked.? if things get to a blocked state in a sprint (that too at the very first column), then why take it in the active sprint (review the Definition of Ready), focus on the sprint planning, increase more collaborative talks with the developers on understanding the problem, have a focused Daily Scrum where most of these blockers actually gets solved within minutes.

Thanks @Sudarshan TS for the detailed response!

Like Sudarshan TS likes this
Sudarshan TS Community Leader Apr 10, 2021

To improve the community answers - We would suggest you to accept the answers :) as you grow in learning.!

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