Automation rule to recover fields to another ticket

[Laetitia Montrichard]

Hello,

When I create a new ticket, I would like to recover data from 5 custom fields from another related on ticket. My two ticket are linked by a "related on" dependencie. My 5 custom fields are the Summary, Description and 3 specific fields. How can I do an automation rule for that?

Thank for help 

[Ste Wright]

Hi @Laetitia Montrichard 

Welcome to the Community.

You can do this using Automation, but what will work best for you depends on the process. Are you looking to...

• Set the fields during creation - and if yes, is it linked to the source ticket at creation always?
• Set fields sometime post-creation (eg. once the linked ticket is added)?
• Trigger by some other process step or stage?

If you can provide this information, I'd be happy to give you some ideas for how best to trigger and then copy the data from the source to the destination issue :)

Ste

[Laetitia Montrichard]

Hello,

yes I tried the solution of Renata below but I did not work.

When I create a new ticket "type X" - I set the field Linked issue to a previous ticket "Type Y" which contains some generic field. 

I validate my ticket Type X and the automative rule complete the fields Type X with the data from the fields Ticket Type Y. 

Thank you

[Renata_Getint]

Hi @Laetitia Montrichard

To automate the recovery of data from 5 custom fields on a "related on" ticket, you can set up an automation rule in Jira to copy the field values when the new ticket is created. Here’s a step-by-step guide:

Step 1: Create a New Automation Rule

1. Navigate to Project Settings > Automation > Create Rule.
2. Click Create rule to start a new automation.

Step 2: Set the Trigger

• Use the Issue Created trigger:
  • Trigger: When an issue is created.
  • Add a condition to check if the new ticket is linked to another ticket via the "related on" dependency.

Step 3: Add a Branch for the Related Ticket

1. Add a Branch Rule / Related Issues action.
2. In the branch options, select Linked Issues and choose the "related on" link type.

Step 4: Copy the Custom Fields

For each field (Summary, Description, and your 3 specific fields), add a Edit Issue Fields action:

1. Click Add Action > Edit Issue.
2. Use Smart Values to copy the field values from the related issue. For example:
   • Summary: {{issue.summary}}
   • Description: {{issue.description}}
   • Custom Field 1: {{issue.customfield_XXXXX}} (Replace XXXXX with the field ID of your custom field.)
   • Custom Field 2: {{issue.customfield_XXXXX}}
   • Custom Field 3: {{issue.customfield_XXXXX}}

Step 5: Save and Test

1. Save your rule and test it by creating a new ticket with a "related on" dependency.
2. Verify that the fields are correctly copied from the related ticket.

Pro Tip

To find the Field IDs for your custom fields:

1. Go to Jira Admin > Custom Fields.
2. Locate the field and click the … menu > View Field Information to find its ID.

If you run into any issues or have additional questions, feel free to ask. We at Getint specialize in helping teams streamline their workflows with custom integrations and automation solutions. Don't hesitate to reach out if you need advanced customization or integrations with other tools like Jira, ServiceNow, or GitLab!

Best regards,
Renata
Getint | Integration & Workflow Solutions

[Janice]

@Renata_Getint We noticed this response has a distinct AI-like formatting. While we're all for embracing new tech, we want remind everyone of the Atlassian community guidelines and Responsible Tech Principles. Put simply, AI can be a great tool for polishing, but your real-world knowledge is what our community values most. We ask the core of your contributions to come from your own expertise.

If you do use AI in your responses the community management team asks members disclose this in responses. We're all about transparency and genuine human connections here. If you have any questions about this, feel free to reach out to communitymanagers@atlassian.com.