How Rules Run in Jira
Formify's rules run inside Jira's own forms, next to Jira's field controls and any other app that changes forms. This page says who rules run for, what people see while a form loads and how to keep rules predictable.
Check who rules run for
Rules run for everyone who opens the form. People need no Formify permission and no setup of their own, only what Jira already asks of them to create, view or transition work items in the space.
If someone sees Jira's message "We couldn't load the UI modifications configuration for this form", Jira didn't load the rules for them. Check their permissions in the space.
Check that the screen is one rules run on
Rules run in the Create dialog, on the work item view and in transition dialogs, each in some kinds of spaces. Screens & Contexts lists the spaces and the places each screen opens from.
A transition without a screen opens no dialog, so no rules run on it. Rules run in Jira's new transition dialog; where a site still shows the older one, it doesn't run them.
Expect rules a moment after the form opens
Jira loads the form first and applies the rules right after. For a moment people can see the form as Jira's own configuration shows it: a field appears before a rule hides it, or a field shows its usual help text before a rule changes it. In the Create dialog and in transition dialogs, a small spinner next to a field's label shows that rules are still loading.
Keep the fields your conditions read on the form
In the Create dialog, people can hide fields for themselves with Jira's Show fields. Jira doesn't pass a field hidden this way to apps, so a rule can't read it in a condition or change it.
- When a rule stops working for one person only, ask whether they hid the field its condition reads.
- Jira's Find your field doesn't know which fields a rule hides. It still lists such a field, though the field stays hidden on the form.
Run Formify next to other apps that change forms
Several apps can change the same form. Jira lets up to five of them act on one combination of space, work type and screen, and ignores the rest.
When two apps change the same thing on the same field, such as its help text or its visibility, the app that finishes last wins. The order isn't fixed, and Jira shows people a notification about the conflict. Keep everything about one field in one app.
Protect data with Jira permissions, not rules
Rules change Jira's forms, nothing else. A hidden field's value still shows in search, list views, the REST API and the Jira mobile app, and a locked field can still be changed by cell edits in the list view, bulk edit, the REST API, Automation and the Jira mobile app. Data that some people must not see or change needs Jira permissions, security levels or workflow properties. See Data & Security.