nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to clone information from custom fields of one issue to another issue

Alex Shirokov

Hi,

I tried to build an automation rule but failed.

I create the first Epic for my project (info Epic) it contains a lot of info (metadata) in the custom fields.

I need to clone these metadata from the first Epic to all other Epics I will create for this project.

I created a custom field "Metadata Epic" that serves as a trigger for other Epics to collect data from... and that was it

I found out how to clone the entire issue BUT not the data from the custom fields.

Many thanks in advance for your help!

Accepted answers

All comments

Ste Wright

Hi @Alex Shirokov

Are you looking to populate this data from the Template Epic, into all other Epics created?

Almost like...

Trigger: Issue Created
Condition: Issue Type = Epic
Action: Edit Issue - copy metadata from Template Epic

What does your current rule look like? And what limitation are you finding? And how do you create these new Epics, if not as a clone?

Ste

Alex Shirokov

Hi Stephen,

thank you for your reply.

How should I show in my rule what is the "Template Epic" is?

I tried to do it via JQL "issuetype = Epic AND text ~ "Project Summary" ORDER BY created DESC"

I do not understand how to map this "Main Epic" to get information to be copied to a new Epic.

Thank you

Ste Wright

Hi @Alex Shirokov

I got this working using two separate Automation rules...

Rule 1: Link to Template Epic
Rule 2: Update new Epic

Rule 1 - Link to Template Epic

Trigger: Issue Created
Condition: Issue Fields Condition - Issue Type = Epic
Action: Edit Issue
- Field: Linked Issues
- Link: clones - TEST-1

Notes:

This creates a link to the Template Epic
The link type can be whatever you like
Whilst it's not obvious, in the Action it is possible to type a Key into the second drop-down - even though it isn't an option in the list.

Rule 2 - Update new Epic

Trigger: Issue Linked - type = Cloners
Condition: JQL Condition - issuetype = Epic and createdDate >= -1m and issueClones = TEST-1
Action: Edit Issue
- Set fields. Set field data using smart values - {{destinationissue.field}}
  - For example Template Epic's Summary = {{destinationissue.summary}}

After creating the rule, go to Rule Details - and check the box next to Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

Notes:

The Rule Details checkbox allows for Rule 1 to activate Rule 2
The Condition ensures it's activating only at creation (i.e within 1 minute)
The Action can set whatever number of fields is required
{{destinationissue}} refers to the Template Epic, in this instance. This smart value can be used in a range of fields.

This works for me! There might be a more elegant option using variables, but I found having multiple custom fields to copy made that overly complex.

Let us know if this could work for you! Or if you have any further questions, please feel free to ask them

Ste

Alex Shirokov

Hi Stephen Wright _Elabor8,

Thank you a million for your reply!

I'll try to replicate what you suggest to do.

Thanks again!

Alex Shirokov

@Ste Wright Thank you very much Stephen!
I’d be happy to get your advise how to achieve my scope.
I just feel a uncomfortable to take your time 🙂.

Ste Wright

Hi @Alex Shirokov

No worries - what is it that still isn't working from the previous answer?

Ste

Ayan Softwares

Hi,

You can achieve this using Automation with Lookup Issues — trigger the rule when a new Epic is created or when the Metadata Epic field is set, then use Lookup Issues and Edit Issue to copy the required custom field values from your source Epic.

If you also need to standardize or manage custom fields and metadata at scale, tools like BOFC (Bulk Object Field Creator) can help streamline field management and ensure consistency across your setup.

Hope this helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud