Copying custom fields across issues under an epic

[BrentBot]

I need a way to copy custom field values across issues under an epic, but the issues are not necessarily linked to each other. The idea is that once story 1 is status `approved`, the fields copy down to story 3

The structure is as follows:

EPIC

story 1 << values exist here

story 2

story 3 >> copy values to this story

[Gaurav]

Hello @BrentBot 

This can be accomplished by using Automation. The trigger can be set as Issue Transition to the required state, validated for issue type, and then the content can be copied.

Please let me know if you need help with the exact rule level details.

[Gaurav]

Hello @BrentBot

As we do not intend to copy the custom fields to all the stories within the Epic, we need to have a connection/ link between the stories to which the fields are required to be copied.

If this link can be defined, then the Automation rule will help in copying the fields from Story 1 to Story 3.

[BrentBot]

There is no way to have the system look for a specific issue under the same epic?

[Gaurav]

Hello @BrentBot 

The system can look for specific issues under the epic but we need to define a condition that will help execute this across different epics.

[BrentBot]

The rule will just need to look for a specific issue type

the rule will be something like:

when an issue is transitioned to status `approved`

and that issue type equals `discovery`

Then certain fields will transfer values down to the issue type `presentation design`

these two issues will not be linked to each other under the `epic`

[Gaurav]

Just to understand the use case better, can there be multiple issues of type 'Discovery' and 'Penetration Design' within an Epic?

In case there can be more than 1 issue of any of these types, then the general rule would copy from each issue of 'Discovery' type when it transitions and copy to each issue of 'Penetration Design' type.

If this is not the case, then it would work as expected.

[BrentBot]

yes there are more issue types under the epic. this would only happen one time

[Gaurav]

@BrentBot Please confirm the following:

• Can a single Epic have more than 1 issue which is of issue type 'Discovery'?
• Can a single Epic have more than 1 issue which is of issue type 'Presentation Design'?

[BrentBot]

no

typically 3-5 issue types of which is discovery and presentation design 99% of the time

[Gaurav]

@BrentBot

In this case, we need to have a connection between which Discovery issue should update which Presentation Design ticket.

If that is not done, then when any one of the Discovery tickets is moved to the Approved status, then all of the Presentation Design tickets would be updated.

I do not think that is the requirement here.

[BrentBot]

that is actually fine if that happens. can you please provide steps that would accomplish that? I am not worried about this case which you have highlighted