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

Is "Pending QA" a 'To Do' or 'In Progress' category



I'm having some discussions with my project leads at the moment regarding the current configuration of our workflows. 
It's a sizeable company with a countless number of Jira projects. 

They all have the Status Category of 'To Do' on 'Pending QA' tasks but there is an argument that the story status is actually 'In Progress' because Pending QA is part of the Definition of Done workflow and not the Definition of Ready and our Release board shows more blue 'To Do' issues than it should and its misleading when release planning. 

Whats your thoughts on this?

1 answer

1 vote

It's really a question of preference... I would say that anything that has been started is "In Progress", whether it is in a holding state or actually being worked on.  I am currently in an organisation where they have lots of the "To Do" statuses, which as you have pointed out can make a mess of the release progress charts.  So my personally view is that you should only have one "To Do" state, only one "Done" state (using the resolution field to differentiate closure reasons), and everything else is "In Progress".

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events