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.

[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 

[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.