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

Can a status be added AFTER Done related to User Confirmation after something is released to prod?


My team is a Company Managed Jira software project. The issue we keep coming across is that the development team and the support team have different definitions of "Done". When the dev team completes work prior to production, they want to mark the story or bug done so it doesn't roll over to another sprint. 

The support team wants to leave the Jira open until the fix is in production and the user confirms the issue is resolved. 

The development team is asking us to remove their Team (related to their active sprint board and metrics) to the support team once they consider it done, but wouldn't that remove it from their team's metrics?

The other solution they had was to have the support team create a Task for follow-up after the main issue is resolved but that's extra work that shouldn't be done. We can look into automation if needed. Not sure if this is something that needs defined on the business end or if someone has found a common solution for both dev and support teams to work together on one ticket. 

Another solution I had was to add a "User Confirmation" status AFTER Done so that way the dev team still gets credit for their work but it's not technically active (even though it is in a way) while the support team verifies the issue.

Does anyone else have experience with this issue and how did you handle it?

1 answer

Hi @Sandy Hayes ,

I can suggest some possible options :

- having a workflow with all steps for both teams and split the status of the workflow between two different boards , one for dev and one for support. So you can match both needs and keep configuration simple.

- have two different issues ( and even two different issue types) , one for dev team and one for support team. Each with their own workflow. And through an automation when the issue of dev team goes to done, you automatically create a linked issue for support team through an automation.

Second option is more complex in terms of configuration but more flexible, each team have their own issues, boards, specific informations if needed , etc…

Does this helps ?


Hi Fabrice,

Thank you so much for these suggestions! I actually like the second option better so I'll look into that solution :)


Like # people like this

Hi Sandy,

Great, have fun in implementing and let me know if you need some help :)
Have a wonderful day,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events