Issue Summary

When there are different fields with the same name, one for Next-Gen project and other for Classic project, it's not possible to differentiate them into the drop-down selection in Automation:

Steps to reproduce

1. Create a Next-Gen custom field in a NG project;

1. Create a custom field with exactly the same name for Classic projects;

1. Create an Automation rule and tries to look for the above fields in one Edit Issue Fields action

Expected Results

When the scope of the rule is restricted to a specific project, it would be nice that the rule itself filter only the applicable fields.

Besides that, for global or multi-project rules, it would be nice to have the id of each field besides its name or even a mention to the project to which this belongs to when it's a NG custom field.