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.
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:
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, and there are several cases to handle. Let's start with a basic one:
The other cases will need additional rules. I recommend considering which you want to support and trying to build the rules, as needed:
To get you started on creating your rules, please refer to these documentation and example sources:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bill, thank you very much,
I'm going to keep trying and experimenting, have a good week!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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}}.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the link between the first issue and the target issue ?
did you start an automation ? Can you show us this rule ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.