You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I'm trying to create an automation to copy a field from child issue to epic, an automation I succeeded in performing before but now this specific field is not cooperating.
*The field is typed "Select List (cascading)"
I added the field to multiple screens in our project.
When I run it, I get the following errors:
Hi @May Azulay
There are several possible causes for this symptom. Four of them are:
Hi @Bill Sheboy
Reviewed all 4 (I'm the admin)
1. When you say the field is not selected for that issue type, are you referring to the field configuration for each issue type? if so, the field is there for all issuetypes I'm trying to copy to. If I'm missing something here, please let me know
2. Reg the issue views - if you are referring to screens, That's cover too. not the issue I guess
3. Jira for automation is still the main actor for performing automation in our project ( I see it on other automation that is active)
4. All issues & Epics are in the same project
Not sure what to do next, appreciate your help
I noticed your rule image, and my first suggestion should have been: try adding a Re-fetch Issue action immediately after the trigger.
The Issue Created trigger can fire so quickly that the issue data is not yet available to the remainder of the rule (i.e., a race-track error). This can cause unexpected behavior the remainder of the rule. Always adding the Re-fetch Issue action with slow the rule by about a second, reloading the data before the steps proceed.
I just noticed you posted an image of the edit, selecting the field from the drop-down list...and that this is a cascading, selection field. That is not supported by automation rules yet, as described in this defect: https://jira.atlassian.com/browse/AUTO-258
The work-around is to use advanced edit with JSON rather than the drop-down list. The defect describes the work-around, and here is some additional documentation on that technique:
Hi @May Azulay ,
The error is related to the copying the value from child to the parent issue.
It all about the inheriting the value from one to another issue, there is something which will impact the process of the action being performed.
To understand the concept of it you can go through the below mentioned linked why we facing this error
Hope that helps you get the resolution!!
Just to make sure we are on the same page, I'm trying to copy a value from the epic issue to its child issue (not backward)
I tried the solution offered in the link and it didn't work.
I also tried to replace "Epic issue" to "Parent issue" and also "trigger issue" but nothing worked.
What can we do?