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 copy a value in secondary issues

Francisco Navarro_zsedh7

Dear community

I need to create an automation that copies the value of the "Epic Type" field (Drop-down list) in the secondary issues that are created, the field that receives the value has the same name.

Accepted answers

All comments

Mohamed Benziane

What is the link between the first issue and the target issue ?

did you start an automation ? Can you show us this rule ?

Bill Sheboy

Hi @Francisco Navarro

What have you tried thus far to solve this need?

If you have a rule that is not working as expected, please post the following to provide more context:

what problem is your rule trying to solve; that is, "why do this?"
an image of your complete rule
images for any rule actions where the field copy is attempted
an image showing the audit log details for the rule execution
explain what is not working as expected, and how you know that

Also, your scenario is unclear to me. Do you have an Epic issue which has a field named "Epic Type", and you want to copy that field to any child issues (e.g., Story, Task, Bug)?

Kind regards,
Bill

Lucas Knorr

Hi @Francisco Navarro
If the second issue is also created in the same automation, you can create a branch and refer to the last issue created here.
You can then create an Edit Issue Action and copy the value of the trigger issue (I guess your first issue?)
The smart value you probably are looking for is {{triggerIssue.Epic Type}}.

Francisco Navarro_zsedh7

Hi Bill

What you mention at the end of your answer is what I need to do, copy the value of the "Epic Type" dropdown field from my parent epic and copy it to the child issues in a field of the same name.

Bill Sheboy

Thanks for that information, and there are several cases to handle. Let's start with a basic one:

trigger: issue field Epic Type changed
condition: issue type equals Epic
branch: to child issues of the Epic
- action: edit issue, copying the field from the trigger issue

The other cases will need additional rules. I recommend considering which you want to support and trying to build the rules, as needed:

when the field changes for the Epic, update the child issues (see above)
when a child issue is created, and has an Epic parent, copy the field
when a child's parent is changed, update the field for the new parent
when a person manually changes the Epic Type field in a child, reset it back to the parent's value
when a child's parent is cleared...what should happen to the field?
etc.

To get you started on creating your rules, please refer to these documentation and example sources:

Francisco Navarro_zsedh7

Bill, thank you very much.

In point 2, how would automation be for that situation? Does it differ in any way from what you describe above? If you have an example, I would appreciate it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation