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
Hi @K Rahul
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see that information...
What type of project are you using: company-managed or team-managed? You may find that information at the bottom-left side of the page expanding area.
If this is a company-managed project, have you asked your Jira site admin if there were changes to the custom field configuration?
Thank you for that information.
It is likely the smart value for the field is different than what you are using. Smart values are name, spacing, and case-sensitive...and they do not always match the displayed field name on the page views. Your field name has a hyphen, and so I expect the smart value is different.
Please try this how-to article to confirm the smart value (or custom field id) for your field, and then use that value. Essentially you do this:
Also, what is the type of your field: text, numeric, etc.?
If it is numeric, that expression can be simplified to this, substituting in your corrected smart value:
And if your field is text, you may use this:
the field is available, same automation is working for other project, field context is also enabled for global projects
The automation issue I am facing, I feel it as a glitch from Atlassian side. Because, the automation works sometimes and it throws error sometimes
Hi @K Rahul ,
Are you an Jira Admin?
Are you able to see the custom field related in your fields or in Settings -> Issues -> Custom fields?
This error might appears if the field has been renamed or deleted recently.
Hope that will helps!