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

Several workflow steps with category done


we have the three workflow steps for finished tickets.

  • Completed (developed and successful tested tickets)
  • Ready4release
  • Done (released tickets)

The workflow steps Completed and Ready4release are currently mapped to the category Progress. This leads to the effect that we need to build a new release before we can close a sprint. I want to decouple the sprint cycles from the release building (release on demand) by changing the category to Done for the workflow steps Completed and Ready4release.

It is running project.

Can this change have any side-effects which cannot be removed anymore?

Thanks for your help!


1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 12, 2021

Hi Torsten - Welcome to the Atlassian Community!

Changing the Status Category of those statuses to a Done category should be fine. Just check the post functions on the transitions to each of those statuses to then set the Resolution field value.

Finally, just realize that it is not the status category of Done that closes the Sprint - it just that the status is in the final column of the Sprint board. So if you move those to a Done status category and you want the Sprint to treat those as closed, then make sure you put those statuses in the final column on the right in your Board settings. 

Hi John!

Thanks for your answer.

We have separate columns for completed and ready4release in the sprint board. When I close the sprint, tickets with the status completed or ready4release will be still moved to the next sprint. Changing the category to done has no effect on this.

Instead, I have to move Completed and Ready4release to the final column in the sprint board but can leave the category on Progress.

Did I understand that correctly?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 12, 2021

Hi @Torsten Waldeck  -- Welcome to the Atlassian Community!

I agree with John's suggestions on "how-to", and...pausing to ask follow-up questions.

You note wanting to decouple development during sprints from release building. So do you want:

  1. To have two separate processes, with sprints for delivery and more kanban-like pull for releases, or...
  2. Do you just want to keep one process to see work, from start to production, for reporting, measurement, etc.?

For the first option, you could create separate release-management tickets, linked to release content tickets, and put the release items on a separate board.

For the second option, you could keep one board, and accept that it takes longer than a sprint for releases to be developed and released to production.  That might incentivize smaller releases.

Best regards,


John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 12, 2021

@Torsten Waldeck  - Basically, yes to your question. 

AND, you should definitely consider @Bill Sheboy 's questions in the process of a final decision. 

It seems that there is one workflow being used with multiple DONE states. And then you can configure board 1 to show up to the first DONE state,  and then board 2 can be configured to show the states from where board 1 left off to the last done.  This will allow you to use one workflow,  but show status that things are moving and closing in a sprint,  even though you only have one story.


How does this affect overall metrics that Jira gathers?  Does velocity and version completion estimation reports still work right?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events