Creating child when issue has been completed

[Alexis Gutierrez]

I'm new to this, I was wondering if it was possible to create a child issue off the parent once the parent has gone through the process and has been completed. I would like for a child to be created so that we can look back to the parent issue to see where it all started from. For example, customer asked for product A, it was sent which completed the issue. However, I would like a child issue created so I can check to make sure product A is what was needed. If not, send out another product. Please let me know if this has been addressed before.

Thank you!

[Hamza Chundrigar · Accepted solution]

Is this parent issue a standard story level issue (with a sub-task being the child issue) or does the epic act as the parent and stories/tasks being child issues?

Either way, you could do this via Automation for Jira.

• You could use the trigger when a parent issue is transitioned to done/completed.
• Then you could add further conditions based on issue fields/JQL/etc (if any) — I don't have the full picture of what you're trying to do so I can comment on this further until I know more.
• Then perform an action in your rule: Create sub-tasks (and add a summary of what that sub-task should be).

[Alexis Gutierrez]

The issue is not an epic. From what I see with the definitions, I create a task on a test board and once it has been completed that task needs a follow up. I would like a child issue or subtask created created so that I know that the main task needs a follow up but it's created a new issue to flow through the board as the main task did. I hope that made sense..

[Hamza Chundrigar]

Gotcha.

At its basic form, you could use something like this - and make modifications as needed.

[Alexis Gutierrez]

Hi, so both of these actions worked for what was needed, thank you so much! However, it created two different boards for the subtasks. Is there a way to fix that? I would like all subtask to show together if possible.

[Mark Segall]

Hi @Alexis Gutierrez and welcome to the community!

Yes, this is a pretty straightforward automation rule.

• TRIGGER: Issue Transitioned (To your Resolved status)
• ACTION: Create Issue

[Alexis Gutierrez]

But does that action create a child issue from the original issue?

[Mark Segall]

Yes - But, what is your definition of "child issue"?  Are you meaning linked?  If so, you can include the Linked Issues field in your Create Issue and set it to link to the trigger issue.

[Mark Segall]

Based upon your response, You would use the Create Issue action as mentioned above and set the issue Type to Sub-Task or even use the Create Sub-Task action.