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

Tickets in customized status being treated as un-done even workflow setup Done category

How should we customized status to be treated as Done tasks, so that when closing current sprint, those customized tickets wont be moved to backlog or next sprint? 

For example, my current project workflow is set up like below.

I will need to verify done ticket across projects' tasks got completed.

So there's actually 2 stages:

One is under design team project design task (In Progress -Done), whose Done status is expected to not be carried to next sprint. 

Another process is when engineering picks up design done work for coding and completes this design development(Pending dev work->Closed), we would like to re-activate ticket and remind designer to verify the engineering's development work.


Currently, if my tickets are under "Pending Dev Work" will still be treated as in-progress tasks. And when completing current sprint, those tickets will be carried to next sprint : (


Is there any magic way to fix this, please? Or anywhere I set up wrongly, please? 


1 answer

0 votes

Hi @Sophie Gao ,

in order to be considered closed, PENDING DEV WORK status should be placed in the last column on the right of your board.

It should fix your issue.

Hope this helps,


Thanks a lot, such a small trick. ; ) Resolved!

You're welcome @Sophie Gao . Please mark my answer as accepted ;)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events