> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/jira-administrator/frequently-asked-questions.md).

# Frequently asked questions

Answers about what Field Rules does, where it runs, how to make fields required, read-only or pre-filled, and how it differs from native Jira.

#### What is Field Rules?

Field Rules lets Jira admins hide fields, make them read-only or required, and pre-fill values based on conditions, from one place and with no scripting required. A rule you create once applies across the spaces, work types and views you choose, in Jira and Jira Service Management. Rules react to field values, work type, user, group, space role, or the transition being performed.

#### Do I need to configure rules in every space?

No. A UI Modification can cover many spaces, work types and views at once, so you configure the logic once instead of repeating it in every space. You choose where it runs when you create it. See the [Setup guide](https://docs.forgappify.com/field-rules/jira-administrator/setup-guide.md).

#### Does Field Rules work in team-managed spaces?

Yes, on the views that Atlassian supports for them. In team-managed spaces, rules work with both global and space-scoped custom fields.

* Create works in company-managed and team-managed Jira Software, Jira Work Management and Jira Service Management (agent view).
* Issue View works in company-managed and team-managed Jira Software and Jira Service Management (agent view).
* Transitions work in company-managed Jira Software, and in company-managed and team-managed Jira Service Management (agent view).
* Create Request works on the customer portal of company-managed and team-managed Jira Service Management.

See [Where rules run](https://docs.forgappify.com/field-rules/about-field-rules-ui-modifications-for-jira.md#where-rules-run) and [Limitations](https://docs.forgappify.com/field-rules/jira-administrator/limitations.md) for the full detail.

#### Does Field Rules require coding knowledge or custom scripts?

No. Every rule is configured through a visual interface - you pick a field, an action, and the conditions that trigger it. No coding knowledge is needed and there are no custom scripts to write or maintain. Field Rules is self-contained, so there is nothing else to install.

#### How do I make a field required only for certain work types?

Use the Make field required rule with a precondition on work type. The field becomes mandatory only when the condition matches - for example, require "Steps to reproduce" on Bug work items and leave it optional everywhere else.

#### How do I make a field required only on one transition?

Use the Make field required rule on the Issue Transition view and add a condition on the transition, for example the transition name or the destination status. The field is required only when that transition is performed - for example, require a "Rejection reason" only when a work item is closed as "Won't Fix". See [Conditions](https://docs.forgappify.com/field-rules/jira-administrator/conditions.md).

#### Can I make a field read-only on transitions or on the customer portal?

Yes. Use the Lock field rule on the Issue Transition views, including the JSM agent view, and on JSM Request Create for the customer portal. Read-only support depends on the field type - for example, checkboxes and radio buttons cannot be locked on the portal. See [Supported fields per view](https://docs.forgappify.com/field-rules/jira-administrator/supported-fields-per-view.md).

#### Can I show or hide fields on the Jira Service Management customer portal?

Yes. Field Rules works on the Create Request screen of JSM portals, and on the agent views inside service projects. You can show and hide fields, enforce requirements, pre-fill values, and update field descriptions, scoped to specific portals and request types. Portal field support is more limited than standard Jira screens - see Supported fields per view.

#### Can I hide work types that are no longer used?

Yes. The Hide issue types rule removes work types from the work type field on Global Issue Create and Issue Transition, including their agent-view versions. It is not available on Issue View or on the customer portal. If the work type currently selected gets hidden, the field switches to the next allowed one.

#### Can I set default values for system fields such as priority?

Yes. Use the Pre-fill field rule. Priority, summary, description and labels can be pre-filled on create, on transitions and on the customer portal. Other system fields, such as assignee, reporter, components, versions, resolution and due date, depend on the view - see [Supported fields per view](https://docs.forgappify.com/field-rules/jira-administrator/supported-fields-per-view.md).

#### How do I create dependent or cascading dropdowns in Jira?

Combine rules: use Hide field options or Change field value so that the choice in one field narrows or sets the options in another, and Show field to reveal a second-tier field only when relevant. Rules run in sequence, so each rule can react to values set by earlier rules.

#### How do I automatically pre-fill a field?

Use the Pre-fill field rule to set a value when the screen loads, before the user interacts. Pre-fills can be chained - selecting a category can set a sub-category and assignee automatically.

#### Can I show different fields to different users, roles, or groups?

Yes. Rules support user preconditions based on group, space role, or individual users. Jira's screens and field configurations vary by work type; user, group and role conditions are what Field Rules adds.

#### Can standard Jira do this without an app?

Part of it. Jira configures fields per work type through screens, field schemes and field contexts. Field Rules adds conditions on another field's value, on the user, group or role, and on the transition being performed. See [Field Rules vs native Jira](https://docs.forgappify.com/field-rules/jira-administrator/field-rules-vs-native-jira.md) for a side-by-side comparison.

#### How is Field Rules different from a scripting app?

A scripting app can achieve much of the same with code that you write and maintain. Field Rules configures the same kind of conditional logic in the admin UI, with no code, and one set of rules can cover many spaces and views.

#### Is there a free plan?

Yes - Field Rules is free for up to 10 users.

#### Where does my data go? Is it secure?

Field Rules carries the Runs on Atlassian badge. It uses only Atlassian-hosted compute and storage, so your data never leaves Atlassian's infrastructure and stays in your instance's region.

#### Can I move my configuration to another Jira site, or back it up?

Yes. Export any UI Modification to a file from the configuration list and import it on the same or another site. Items that cannot be matched automatically between the two sites are resolved by you during the import. See [Import and export](https://docs.forgappify.com/field-rules/jira-administrator/import-and-export.md).

#### How many rules can I have?

There is no strict limit on the number of rules you can create. Rules are stored under *UI Modification*, and each UI Modification can store up to 50,000 characters of configuration data.

In practice, you may eventually reach this limit if you use a large number of rules or very complex preconditions, but this is unlikely in most cases. If you do reach the limit, please contact us for assistance.

#### Why don’t my rules work on the Transition screen?

**Potential cause:** You or other users may still be using the **old Issue Transition experience**.

The app relies on Atlassian’s **UI Modifications API**, which is supported **only in the new Issue Transition experience**. Rules will not be applied when work items are transitioned using the legacy experience.

**How to fix this**

Ensure that the **new Issue Transition experience** is enabled for all users who expect the rules to apply.

Atlassian explains how to enable or disable the new experience in this post:\
[Try the new issue transition experience in Jira](https://community.atlassian.com/forums/Jira-articles/Now-GA-try-the-new-issue-transition-experience-in-Jira/ba-p/2734436)

With the new navigation, users can manage this setting directly at:\
`/jira/settings/personal/general`

Once the new experience is enabled, Field Rules will be applied during work item transitions as expected.
