How to copy a value in secondary issues

Francisco Navarro
Contributor
October 22, 2024

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.

3 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 22, 2024

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

Francisco Navarro
Contributor
October 23, 2024

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2024

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:

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

 

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

 

Francisco Navarro
Contributor
October 23, 2024

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.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2024

First things first:

Successfully using Jira Automation requires learning and experimentation.  When one just uses rules provided by others, whether from the community or Atlassian templates, without understanding the rules, one will be unable to maintain and improve them.  I have provided several references to help you pause and learn more about creating rules.

And as a reminder, the Atlassian Community is a place for people with similar interests to learn and collaborate.  It is not a free labor pool to implement requests upon demand.  If your team regularly needs more assistance with automation I suggest hiring a full-time, experienced Jira Administrator to help.

 

To your follow-up question, the rule would have a different trigger, conditions, etc. for that case.  Please review the available rule triggers to learn more: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

Francisco Navarro
Contributor
October 23, 2024

Bill, thank you very much,

I'm going to keep trying and experimenting, have a good week!!

Like Bill Sheboy likes this
0 votes
Lucas Knorr
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 22, 2024

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

0 votes
Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 22, 2024

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

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events