Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Linking Epic's sub-tasks in a waterfall workflow

How can I make the next in row sub-task to move to In Progress and notify assignee when previous task is set to Done?

1 answer

0 votes
Mirek Community Leader Feb 03, 2021

So just to clarify..  you have for example a Parent Task with 5 Sub-Tasks that are executed in specific order and you want to move the next one to In Progress when the previous is Done?

Do I understand correctly?

Yes exactly. There would need to be a condition though as may happen that sub-task assignee may be in Unassigned state so then obviously this can't progress without a valid assignment.

Mirek Community Leader Feb 14, 2021

Would not be more natural to simply modify the parent workflow and since we cannot start sub-tasks simultaneously design it in a way that next status is the work that need to be done (currently defined in a sub-task)?

Example:

Parent workflow (TODO / IN PROGRESS / DONE)

Sub-Tasks
* Do desing
* Implement
* Test..

so combining this to single ticket it would be

TODO / DESIGN / IMPLEMENTATION / TESTING / DONE..

I do not quite understand the idea of creating 5 Sub-Task on the beginning if we wait for previous state to be completed.

Oh it's because they're completely repetitive. All that changes is assignees at different  stages. It's not a software related project but rather an ongoing process where the same set of tasks is done for different clients so all that changes is the parent Epic name and as mentioned, the sub-task assignees. The transition is mainly to inform the next in row assignee to start processing as their clock started ticking.

Mirek Community Leader Feb 19, 2021

Well you can still change assignee automatically in a post function when transitioning an issue.. Would that not work?

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you