-
Suggestion
-
Resolution: Unresolved
Issue Summary
If we have multiple Jira fields with the same name, for example a custom field Priority same as the system field Priority, different automation components will display them with different suffixes, some triggers/conditions will show Priority (priority) for the system one:
Whereas Edit Issue actions will show it as Priority (System)
Suggestion
Follow a naming convention, so the affected fields are uniformly identified under different components.
- is related to
-
AUTO-161 Automation fails when it has two fields with the same name/type, showing the error "Found multiple fields with the same name and type:" and Additional fields contains invalid field(s) in 'update' or 'fields' section. <field_name>"
-
- Long Term Backlog
-
-
- Gathering Interest