how do i make cloned tasks link to a task that triggered it with a manual trigger?

[Una Horne]

first time writing here, let me try to be as detailed as possible.

the kind of work my team does requires scheduled maintenance on a particular ongoing task. in our previous task keeping software, when the maintenance task was completed, it would automatically create a new copy of that task, and add it to the ongoing list of tasks nestled in the "master" task. this was very convenient for tracking what tasks were getting completed and which ones were missed.

id really like to recreate that in jira. the issues i am running into is the automation that would enable this.

the way i have it set up to generate the first maintenance task is through a manual trigger. the button is pressed, and the task generates with the correct link. heres where things are breaking.

after the status changes from "scheduled" to "done", the idea is that the same task would appear directly below the completed one in the main task. but what is happening is the new clone is linking itself to the completed task.

i have also tried utilising the "scheduled" automation to have the tasks clone themselves at a set cadence, but still i am unable to make them appear in the trigger task.

if more context is needed: all of our requests/issues are the same level in hierarchy. all are set to zero. we are not utilising sub tasks, epics, parents, etc. at this time.i have tried many different pathways in the automations to try to get this to work but i am at a loss here, wondering if this is even possible at this point. any help would be great

[Una Horne · Accepted solution]

FYI if anyone stumbled upon this question, i have fixed it. simple and effective.

[Christopher Yen]

Hi @Una Horne welcome to the community! 

I previously made a recurring task for a recurring work order type of situation that you may be interested in recreating

Essentially I created a new issue type called "Recurring Task" which serves as the master / parent task and then added two custom fields of "Frequency" and "Next Trigger Date". Using the scheduled automation it will check any recurring tasks if the next trigger date = today then create a linked task that copied all the details from the parent recurring task and then push out the next trigger date by 1 day, 7 days, 30 days, etc depending on what the frequency is. 

[Una Horne]

@Christopher Yen  thanks for the reply! i dont think this is the solution im looking for unfortunately, but i appreciate the help

[Joseph Chung Yin]

@Una Horne 

Welcome to the community.  Need some clarifications from you -

1) You already have an automation setup where when the master issue is Completed (meaning issue is transition to the terminal status), it will automatically cloned itself in creating the new task working right?

2) Is the new task issue linked back to the master task established too?  How are new task issue link conducted?  Manually or through automation?

Keep in mind, once the issue links are established, it will always show up in the master task regardless whether if the cloned issue is done or completed.

Can you provide us on how you have configured your automation rules (screenshot of your rules etc...) with the steps?  So we can advise further.

Looking forward to your updates.

Best, Joseph Chung Yin 

[Una Horne]

hey Joseph thanks for replying!

1 - clarification on the master issue: the master issue is ongoing, set to "in progress" while maintenance tasks occur on a set cadence

2 - the new task is linked to the master task within the manual trigger automation. trigger is pulled > new task is created > task is linked to trigger task

the automation is pretty simple and straight forward for creating the task