how assign to subtask automatically in Jira automation ?

[jeevan]

Hai @John Funk 

I have a demo Jira project and I created 4 four workflows, in that workflows, one of the workflows is the main and the remaining 3 workflows are sub-task workflows (like design and coding, and testing workflow)

The main workflow is open to design to coding to testing to Done

design workflow is like open and design in progress and review and close

same as like coding workflow and testing workflow

Actually what my requirement is,

When a story is created and that story moves from open to the designer status then automatically create 3 types of  sub-task like 

1st sub-task name is the design subtask

2nd sub-task name is coding       "

3rd sub-task name is a tester        "

In the story, I used a single-user custom field for the designer, coding, and tester.

I used a validator like while a story moves from open to design, please mention the designer name, coder name, and tester name.

when the created story reaches design status the 1st design sub-task will automatically assign to the designer and the remaining  sub-task will not assign to 2 sub-tasks

when the designer completes the 1st sub-task then the 2nd sub-task will assign to the coder automatically and the parent story also moves to the coding status. He completes the coding sub-task then the 3rd sub-task will assign automatically to the tester and the parent also moves to the tester status.

And last, when these three subtasks are completed then the parent-like story also will reach to done status 

how it is possible in Jira automation rule?

please help me

thanks in advance

regards

Jeevan Kalyan

[John Funk]

Hi Jeevan,

There's a lot going on here. Can you post your actual rule and then identify the part that you need help with? 

[Gaurav]

Hello @jeevan 

Before planning and creating the automation rule, can you confirm the following:

• How are the designer, coder and tester for the sub-tasks of a story defined? Are these mentioned in the story?
• Is the story transitioned to the next state when a sub-task is completed?

These will help create the automation rule.

--GG

[jeevan]

Hai @Gaurav 

thanks for your reply.

In the story, I used a single-user custom field for the designer and coding, and tester.

I used a validator like while a story moves from open to design please mention the designer name and coder name and tester name.

Actually what my requirement is,

When a story is created and that story moves from open to the designer status then automatically create 3 types of  sub-task like 

1st sub-task name is the design subtask

2nd sub-task name is coding 

3rd sub-task name is a tester

when the created story reaches design status the 1st design sub-task will automatically assign to the designer and the remaining  sub-task will not assign to 2 sub-task

when the designer completes the 1st sub-task then the 2nd sub-task will assign to the coder automatically and the parent story also moves to the coding status he completes the coding sub-task then the 3rd sub-task will assign automatically to the tester and parent also moves to tester status.

And last, when these three subtask is completed then the parent also will reach to done status