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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to create a simple automation that:
When I test this automation it fails each time with a:
The field Incident Source is most definitely in the issue type:
Here's my automation:
Is there a way to debug this any more than what is being shown? Any help would be appreciated.
Some quick question to help diagnose this...
Who is the rule actor for that rule, set in the details at the top of the rule? Is it still the default of Automation for Jira? If that was changed the triggering user may not have access to the field.
What type of project is this rule in: company-managed or team-managed?
What is the scope of the rule: project, multiple-project, or global?
Is that a custom field, or from a marketplace addon?
If it is a custom field the team added, what is the type of that field?
And, is that field on the views for add / edit of issues?
FYI, please try to stay to one conversation thread. That will help others reading this thread in the future know if there are multiple solution approaches to try. Thanks!
You note the field is cascading, yet the screen image seems to indicate something else. My understanding is the cascading fields can only be edited with JSON in automation rules.
Would you please post an image showing that Edit Issue Fields action?
That is interesting!
I am trying this with a Free license, and cannot edit a cascading, custom field using an automation rule, edit issue action's drop-down list. The JSON edit is the only option.