Is anyone else having issues with the way custom fields in Automation for Jira is handling? One week all my custom fields need to be referred to as {{issue.customfield_<number>}} and the next week it won't trigger and I'll have to go back to the field name such as {{issue."New Customer"}} and vice versa.
I am not seeing that symptom for our rules. Is that a custom field for the instance (company-managed projects) or for a specific, team-managed project?
Other than checking in with your site admin about any recent custom field changes, consider asking the site admin to submit a support ticket to Atlassian: https://support.atlassian.com/contact/#/
They may be able to see something in your instance's logs to clarify what is happening.
Best regards,
Bill
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.