Is there a way to generate a comprehensive list of fields associated with automation?

[Farhad Malegam]

We currently have automation set up with a number of triggers over the years. We are now reviewing our fields and are in the process of making changes to them. Is there a way to collate a list of all fields that are associated with automation? This would be immensely helpful in ensuring automation rules are not affected. Thank you

[Bill Sheboy · Accepted solution]

Hi @Farhad Malegam -- Welcome to the Atlassian Community!

First thing, I am just another Jira user and have no knowledge of automation engine internals or Atlassian decision-making.  With that out of the way...

I suspect the answer to your question is: "no".

Although Atlassian products have been around for a while, they continue to rapidly evolve...including what is / is not supported by automation rules.  Some times the different teams in Atlassian account for changes and automagically update rules for us when things deprecate.  Some times, they do not.

Without knowing more about your scenario and the changes you are making, I recommend:

• work with your Jira site admin to inventory all of your Atlassian products and marketplace addons
• inventory and identify what your rules try to accomplish, in general; ideally document rules which use specific features, perhaps with rule export and searches of the JSON.  (Such research is becoming easier with the improvements to rule, list filtering: https://community.atlassian.com/t5/Automation-articles/Automation-Rules-List-filtering-is-here/ba-p/2670061)
• identify example Jira issues using the various features and addons
• using this documentation, review the currently documented smart values and supported JQL field names 
  • https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
  • https://support.atlassian.com/jira-software-cloud/docs/jql-fields/
• using this how-to article, identify the smart values for your example Jira issues
  • https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
• review the documentation for your marketplace addons to learn if they use static or dynamically generated fields for issues; this can save a lot of frustration trying to edit an addon's data with a rule
• add watches to the Atlassian community areas to watch for articles on field and feature changes

Kind regards,
Bill

[Farhad Malegam]

Thank you @Bill Sheboy 

I'll give this a go.