> 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/rules/make-field-required.md). # Make field required Converts an optional field to required based on conditions. When conditions are met, the field is marked as required and the user must fill it in before submitting. When conditions are no longer met, the field returns to optional. **Supported contexts:** Global Issue Create, Issue Transition, JSM Request Create. *** ## How it works When the screen loads or the user changes a watched field, the rule re-evaluates the preconditions. If they pass, the field is marked as required. If the field is currently hidden, it is automatically shown - a required field must always be accessible to the user. If the field is already required (by Jira system configuration or another rule), the rule is skipped. *** ## Configuration | Option | Description | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Target field** | The field to make required. | | **Preconditions** | Optional field and/or user conditions. When conditions are met the field is required; when not met it remains optional. Leave empty to always make the field required. | *** ## Supported fields The rule is not supported on Issue View - the `setRequired` operation is a platform limitation on that screen. On the supported views, not all fields support this operation. Key exceptions: * **Issue Type, Resolution, Status, Summary, Original estimate** - not supported on any view. * **Assignee, Components, Multi user picker, People, Project picker, Reporter, URL, Target start, Target end** - only supported on Global Issue Create. * **Affects versions, Fix versions, Checkboxes, Radio buttons, Parent** - supported on Global Issue Create and Issue Transition only. * **Select, Multi select** - supported on all three views. * **Priority** - supported on all three views. * **Date picker, Date time, Due date, Number, Text field, Paragraph, Description, Labels, User picker, Cascading select** - supported on Global Issue Create and JSM Request Create. *** ## Interaction with Show field If a field is hidden by the [Show field](/field-rules/rules/show-field.md) rule and then made required by this rule, the field is automatically shown. This prevents creating a state where a required field is inaccessible. Conversely, the Show field rule will not hide a field that is currently required. Whichever rule runs first, required fields remain visible. *** ## System-required fields Fields already marked as required by Jira's screen or field configuration cannot be made optional by removing or disabling this rule. The rule only works in one direction - it can make optional fields required, but cannot override system-level requirements. *** ## Examples **Conditional required field**\ Make a "Steps to reproduce" paragraph field required when the Issue Type is set to "Bug". For all other issue types the field remains optional. **Required field for a specific group**\ Make the "Severity" field required for users in the "Support" group. Other users can leave it empty. **Required field based on another field's value**\ Make the "Root cause" text field required when a "Defect confirmed" checkbox is selected. The field only appears and becomes required after the user checks the box - combine with the [Show field](/field-rules/rules/show-field.md) rule for the full effect. **Required field based on resolution**\ When transitioning an issue and the Resolution is set to "Won't Fix", make a "Rejection reason" paragraph field required. This ensures that whenever an issue is rejected, the team must document the reason before the transition completes. *** ## Known limitations * **Issue View is not supported.** The `setRequired` operation is not available on Issue View - this is a platform constraint. * **System-required fields cannot be made optional.** The rule only converts optional fields to required, not the other way around. * **Many fields have limited view support.** Several field types only support this operation on Global Issue Create. See the exceptions list above. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.forgappify.com/field-rules/rules/make-field-required.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.