Field Rules - UI Modifications for Jira

Waiting for could 2 cloud migration support from Atlassian Alternatively provide import / export mechanism with UI confirming mappings for projects, issue types and fields

In some cases conditional logic to hide fields would be much clearer that Show field, which requires reverse conditions

Currently when making template fields, if you are using a paragraph field (like description), Field Rules only accepts text. This means formatting like headings and colors are not available.

For operator: contains all of (A, B), the reverse is: contains non of A OR Contains non of B Could we have operator like "contains not all of" that would simplify the opposite of contains all of

The issue status is not available in the UIM API during an issue transition. To work around this, the status value can be retrieved via the REST API.

The group itself could have preconditions. This would allow setting preconditions once for all rules, while still enabling additional conditions to be added within individual rules.

The Pre-fill field rule works only on screen load (create and transition). The Set field rule would allow reacting to changes after the initial screen load, and it would also work on the issue view. Settings: [x] Overwrite if not empty

It would be easier to configure more than one field per rule. For example, the Make Field Required rule could allow selecting multiple fields, with preconditions executed only once for all added fields.

Often, these two rules come in pairs, so it would be easier to configure them using an additional checkbox—especially when there are many preconditions.

It will allow reacting to field changes and displaying a warning or error flag on the issue view. It could be used in addition to workflow validators that reject the transition. With a Show Message rule, you would be able to validate the field before initiating the transition.