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

How to attach sub-workflows to statuses of the main workflow ?


Hello friends! I have another problem.

I have 5 workflows that are included in the same workflow schema.
One of the workflows is the main one. The other 4 are as sub-workflows that correspond to each status in the main workflow.

I need these 4 workflows to be associated with the statuses of the main workflow. That is, when I create a issue, it should have the first status of the first sub-workflows.
Further, it is also necessary that there was a transition from the last status of a sub-workflow to the first status of the next sub-workflow.

I think it can be done with groovy (may be by post functions), but have no idea how to implement it.
Perhaps I did not fully describe everything. I can tell you in detail if you need.

I will be glad to receive your answers!

1 answer

1 accepted

1 vote
Answer accepted

There is no such thing as sub-workflows as you have defined them here.  By definition of status, an issue can only be in one istatus at a time, otherwise your reporting on status is nonsense.

You will either need to define your status as a single level and then build something that groups status together (similar to the status category that jira has already) or start breaking your issues down into sub-tasks that block the movement of their parents forward until they are complete.

Thanks Nic!
I think I figured out how to solve this.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events