How to create recurring ticket with a custom field?

[Antonia]

Hello, I have built a custom field that contains a date. The field is called ‘Reopening date’. When the ticket reaches this date, a new ticket should be created with the same information, such as in the priority or in the description. The ticket should be assigned to the person who set the date. The ticket should also have the same task type and be created in the same project. How do I do this? I've already looked into the automations, but I'm not really getting anywhere. I found this article good, and it comes close to my requirements: https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862#M6570 But after the second step I can't get any further because the screenshots are missing. 

Does anyone have a similar rule that they could make available to me? Screenshots of each bubble will do, of course.

[Duc Thang TRAN]

Hello @Antonia 

I think you need two automation rules:

• First Automation

Trigger: When the field "Reopening Date" changes.
Action: Copy the value of the "Initiator" field into a new user picker field, let's call it "Initiator Reopening Date".
This prepares for the next automation .

• Second Automation

Trigger: Scheduled (daily) using a JQL query like: "Reopening Date" = startOfDay()
Action: Clone the issue, copying the necessary fields, and assign it to the user in "Initiator Reopening Date".
Hope this helps inspire you to create the automation!

[Antonia]

Hi, thank you very much for your answer. Unfortunately I don't see any action that can copy a value. I could only say that the issue should copy itself.

[Duc Thang TRAN]

@Antonia 

From clone action

You can choose the values that don't need to be cloned and decide which fields should have their values copied.

here is a exemple 

[Antonia]

Thank you. But "Copy the value of the "Initiator" field into a new user picker field," How can I copy something into another field?

[Duc Thang TRAN]

@Antonia 

"You can click on the three little dots and choose the copy option, then click on the line to choose the source and the field that needs to be copied

You can read from this kb atlatssian

https://support.atlassian.com/automation/kb/automation-for-jira-different-ways-to-copy-the-value-of-a-field-into-another/

[Antonia]

I did it this way, but it still doesn't make sense to me because I can't specify where to copy it to. You yourself wrote “into a new user picker field”, but I can only select the source. Should I just leave it as it is and carry on? 

In this manual there is also another component, they use the “Edit operations” and not “Clone operations” does that make a difference?

[Duc Thang TRAN]

@Antonia 

Same for clone or edit , you need to click on the line (For erxemple here Add Approuvers from current issue) to choose the source (drop down menu) and the field (drop down menu ) that needs to be copied

[Antonia]

@Duc Thang TRAN 

Hi, thank you very much for trying to help me. Do I have to create a new field? Because our tickets have the “Assigned person” field right from the start.

[Duc Thang TRAN]

Hello @Antonia 

You would need admin instance rights to create a new custom field.

Depending on the purpose of your custom field 'Assigned Person', if this field is available and doesn't impact other reporting, you can start by creating an automation using this field, as I suggested in my first comment.
If this field is not available, or if you're referring to the 'Assignee' field (the default Jira field), it's better to request admin instance rights to create a new custom field

[Antonia]

Hello!

Thank you, yes I meant the "Assignee" field (Default). Can I just use this field? Or do I have to create a completely new field for this rule? I have admin rights.

[Duc Thang TRAN]

Hello @Antonia 

You can use "Assignee" as long as it doesn’t affect other reporting.

To summarize:

• Automation 1: When the "Reopening date" changes, assign the ticket to the initiator.
• Automation 2: Runs once per day whit jql "Reopening date" = startofday(), it clones the ticket and copies the assignee from the trigger issue to the new issue.

[Antonia]

Hello @Duc Thang TRAN

thanks again for the instructions. However, I still have a problem. When I set the reopening date, the ticket is created immediately and not only when the reopening date is.
For example:
We have today 11.03.2025, I set the reopening date to 12.03.2025 and still the ticket is created on 11.03.2025. I have also used JQL. The screenshot shows “Wiederöffnungsdatum” in the JQL, which is the reopening date in German. The Screenshot is from the second automation.

[Antonia]

Hi, I had also entered a start date with a time. Now a clone of the trigger ticket is created every day at this time, so something is wrong.

[Duc Thang TRAN]

Hello @Antonia 

You may edit the reopening date on a ticket, but the automation finds other tickets where the reopening date is today.
You can check the audit log to see which tickets the automation has processed

also you can click on validate query to find if they are other ticket in this situation 

[Antonia]

Hello @Duc Thang TRAN

then you would still need an automation where the old tickets with the reopening date delete the date. Otherwise, new tickets would be created because the old tickets still have a date set, wouldn't they?

I have now deleted all tickets with the reopening date and created a new one, but a ticket is created immediately and not only when the date is reached.

[Duc Thang TRAN]

@Antonia 

I have now deleted all tickets with the reopening date and created a new one, but a ticket is created immediately and not only when the date is reached.

Regarding this part, the issue may be caused by another automation you showed me earlier. It creates a ticket whenever the "Reopened Date" is changed.
In any case, the automation scheduled, it will immediately create a new ticket when you update the "Reopened Date" of an issue—unless you make the change right before the automation’s scheduled time.

Let’s start from the beginning. I suggested creating two automations:

 The first automation is to capture the value of the initiator who changes the "Reopened Date."

 The second automation is scheduled—ideally to run in the morning (1 per day ) . It will take all tickets where the "Reopened Date" is today, and then it will clone a new ticket based on those.

[Antonia]

@Duc Thang TRAN 

The one in the picture is the first automation. I actually made it the way you said. I also found it strange because you said that I should copy the value from the initiator field and use ‘clone’ for it. So what other action should I use? 

First Automation:

[Duc Thang TRAN]

Hello @Antonia 

Maybe I misunderstood some parts, but if you look at my first suggestion:

• The first automation/action assigns the ticket to the initiator and not to a cloned ticket.The goal of Automation 1 is to keep the value that changes the reopening date,
• in order to help Automation 2 use this value to create a new ticket.

So here is a exemple : 

[Marlene Kegel - codefortynine]

Hello @Antonia,

I am Marlene, product manager of Deep Clone for Jira.

If copying the field values is too complex with Jira Automation - or if you want to reduce the number of you automations - you could check out our app.

You could also set up a template issue, and then set up an Jira Automation that triggers a Deep Clone using Looping Transitions.

- Set up a template issue by simply creating an issue with the needed information.

- Add a Looping Transition and a Deep Clone Post Function to the issue's workflow.

- Integrate Jira Automation with Deep Clone for Jira

If you have question on that topic, feel free to reach out to us directly.

[Gabriel Teixeira]

Hello Antonia!
Ypu will need two Automation.

First one:

Trigger: "Reopening date" Changed
Action: Edit Issue, editing user picker field with the initiator smartvalue "{{initiator}}"

Second one:

Trigger: Daily with JQL: "Reopening date" >= startOfDay() AND "Reopening date" <= endOfDay()
Action: Create a new issue, copping the necessary field values from the Trigger issue 

[Antonia]

Hello Gabriel, thank you for your answer! But why would I need in the Trigger "endOfDay()"?

[Gabriel Teixeira]

whith this JQL, you will ensure that the "Reopening date" is equals today

[Antonia]

A ticket is to be created or cloned when the reopening date is reached.
So if I set the date to 15.03.2025, then the new ticket should also be created on 15.03.2025 and not on the day when I updated the field.

Is your JQL still correct?

[Gabriel Teixeira]

Exactly, this JQL is using the field "Reopening Date"
So when the date set in the field reach, the issue will be returned at the JQL results, cause the automation trigger will be set to run this automation daily.

Trigger: Daily with JQL: "Reopening date" >= startOfDay() AND "Reopening date" <= endOfDay()
Action: Create a new issue, copping the necessary field values from the Trigger issue