Supported Field Types
Dynamic Screen Rules works with system fields and custom fields through Atlassian's UI Modifications API. This page lists all supported field types and explains what each field is used for.
Understanding which field types are supported helps you plan rule configurations and know what's possible with Dynamic Screen Rules.
System Fields
System fields are built-in Jira fields available in all projects. Dynamic Screen Rules supports all major system fields.
Text and Description Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Summary | summary | Issue title/summary | Show/hide, require, pre-fill issue titles |
| Description | description | Issue description (rich text) | Show/hide, require for specific types, change label |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Example Use Case: Require Description for high-priority bugs, hide for simple tasks
Select and Priority Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Priority | priority | Issue priority level | Limit to P1/P2 for bugs, require for incidents |
| Issue Type | issuetype | Type of issue (Bug, Story, etc.) | Limit available types, pre-select based on project |
| Resolution | resolution | How issue was resolved | Limit to technical resolutions for bugs |
| Status | status | Current workflow status | Use in conditions (can't modify directly) |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description, Limit Options
Example Use Case: Show only "Fixed" and "Won't Fix" resolutions for bugs in Done status
User Assignment Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Assignee | assignee | User assigned to issue | Auto-assign based on priority, require for critical issues |
| Reporter | reporter | User who created issue | Pre-fill with current user, lock to prevent changes |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Example Use Case: Auto-assign critical issues to team lead using currentUser() Smart Value
Multi-Value Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Labels | labels | Freeform tags | Auto-add labels based on type, require for specific workflows |
| Components | components | Project components | Pre-fill based on issue type, require component selection |
| Fix Versions | fixVersions | Versions where issue will be fixed | Limit to unreleased versions, lock after deployment |
| Affects Versions | versions | Versions affected by issue | Limit to recent versions, require for bugs |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Limit Options Support: Fix Versions and Affects Versions support option limiting; Labels and Components do not
Example Use Case: Limit Fix Versions to only current sprint versions for in-progress issues
Hierarchy Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Parent | parent | Parent issue (for subtasks/child issues) | Require parent for subtasks, limit available parents |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description, Limit Options
Example Use Case: Require parent issue for all subtasks
Date and Time Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Due Date | duedate | Issue due date | Set to next business day, require for high-priority |
Supported Actions: Show/Hide, Required, Lock, Set Value (with Smart Values), Change Label, Change Description
Example Use Case: Auto-set due date to 3 business days from today using today().plusBusinessDays(3)
Time Tracking Fields
| Field Name | Field ID | Description | Common Uses |
|---|---|---|---|
| Original Estimate | timeoriginalestimate | Estimated time to complete (seconds) | Require for large stories, hide for simple tasks |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Note: Time values are stored in seconds (e.g., 3600 = 1 hour)
Custom Field Types
Custom fields are created by Jira administrators. Dynamic Screen Rules supports all standard custom field types.
Text Entry Fields
| Field Type | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| Text Field (single line) | textfield | Short text input | Show/hide, require, pre-fill with static text |
| Paragraph (multi-line) | textarea | Long text input | Require for detailed explanations, change label contextually |
| URL Field | url | URL input with validation | Show for external bugs, require documentation link |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Example Use Case: Require "External Link" URL field when "External Bug" checkbox is selected
Select Fields (with Options)
| Field Type | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| Select List (dropdown) | select | Single-choice dropdown | Limit options by context, pre-select default |
| Radio Buttons | radiobuttons | Single-choice radio buttons | Limit options, require selection |
| Multi-Select | multiselect | Multiple-choice dropdown | Limit available choices, require at least one |
| Checkboxes | multicheckboxes | Multiple-choice checkboxes | Limit options, pre-select common choices |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description, Limit Options
Example Use Case: Limit "Environment" select field to show only "Production" and "Staging" for critical bugs
User Picker Fields
| Field Type | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| User Picker (single) | userpicker | Select single user | Auto-assign, require approval from specific user |
| Multi User Picker | multiuserpicker | Select multiple users | Require reviewers, pre-fill with team members |
| People (group) | people | Select user with group context | Team assignment, role-based selection |
Supported Actions: Show/Hide, Required, Lock, Set Value (with currentUser() Smart Value), Change Label, Change Description
Example Use Case: Pre-fill "Reviewer" field with current user using currentUser() Smart Value
Date and Time Fields
| Field Type | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| Date Picker | datepicker | Date selection (no time) | Set review dates, require completion dates |
| Date Time | datetime | Date and time selection | Schedule deployments, track timestamps |
| Target Start | jpo-custom-field-baseline-start | Advanced Roadmaps start date | Project planning, roadmap dates |
| Target End | jpo-custom-field-baseline-end | Advanced Roadmaps end date | Project planning, roadmap dates |
Supported Actions: Show/Hide, Required, Lock, Set Value (with Smart Values), Change Label, Change Description
Smart Values Support: All date fields support Smart Values like today(), nextMonday(), addDays(), etc.
Example Use Case: Auto-set "Review Date" to next Friday using nextFriday() Smart Value
Number Fields
| Field Type | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| Number Field | float | Numeric input (decimal) | Budget calculations, cost tracking, scoring |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Example Use Case: Require "Estimated Cost" when issue type is Feature
Advanced Fields
| Field Type | Jira Type ID | Description | Supported? |
|---|---|---|---|
| Cascading Select | cascadingselect | Two-level dropdown | ✅ Supported |
| Project Picker | project | Select related project | ✅ Supported |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description
Note: These advanced field types have complex value structures. Consult documentation for Set Value usage.
Service Management Fields
Fields specific to Jira Service Management (JSM) projects.
| Field Name | Jira Type ID | Description | Common Uses |
|---|---|---|---|
| Request Type | vp-origin | JSM request type | Limit available request types, pre-select based on customer |
Supported Actions: Show/Hide, Required, Lock, Set Value, Change Label, Change Description, Limit Options
Example Use Case: Limit Request Type to "Incident" and "Problem" for internal users
Not Supported Fields
These field types are not currently supported due to Atlassian API limitations:
- Sprint field (Agile boards) - Jira Software specific field with limited API support
- Story Points - Known platform issues with Story Points field modification
- Attachment field - File uploads not supported by UI Modifications API
- Epic Link - Deprecated in favor of Parent field (use Parent instead)
- Custom fields not listed above - Very rare or third-party custom field types may not be supported
Field Type Categories Summary
By Capability
Fields that support Limit Options:
- Priority, Resolution, Issue Type, Parent
- Fix Versions, Affects Versions
- Request Type (JSM)
- All custom select fields (Select List, Radio Buttons, Multi-Select, Checkboxes)
Fields that support Smart Values (Set Value):
- All date/time fields (Due Date, Date Picker, Date Time, Target Start/End)
- User picker fields (
currentUser()Smart Value) - Text fields (static values)
- Number fields (numeric calculations)
Fields with read-only access:
- Status (can use in conditions, cannot modify directly - use Jira workflows instead)
Fields that support Validation Rules:
- All field types support presence validations (Must not be empty, Must be empty)
- Date fields support date validations (After today, Before today, After/Before field, At least X days ahead)
- Number fields support number validations (Greater than, Less than, Between, Not zero)
- Text fields support text validations (Min/Max length, Contains, Not contains)
See Validation Compatibility section below for detailed breakdown.
Validation Compatibility by Field Type
Field validation rules enforce data quality and business rules at the point of data entry. Different field types support different validation types based on the data they contain.
Presence Validations (All Field Types)
Supported validations:
- Must not be empty
- Must be empty
Compatible with:
- All system fields (Summary, Description, Priority, Assignee, Reporter, etc.)
- All custom fields (text, select, date, number, user picker, etc.)
Use cases:
- Conditional required fields
- Ensure fields are cleared in certain workflow states
- Context-aware validation
Date Validations
Supported validations:
- Date after today
- Date before today
- Date at least X days in future
- Date after another field (cross-field)
- Date before another field (cross-field)
Compatible field types:
System fields:
- Due Date
Custom fields:
- Date Picker (
datepicker) - Date Time (
datetime) - Target Start (
jpo-custom-field-baseline-start) - Target End (
jpo-custom-field-baseline-end)
Use cases:
- SLA enforcement (Due Date ≥2 hours from now)
- Date sequencing (End Date > Start Date)
- Planning horizon validation (Release Date ≥30 days ahead)
- Prevent past/future dates
Example:
Field: Due Date
Validation: Date at least X days in future
Days: 0 (allows today and future)
Message: "Due Date must be at least 2 hours from now for Critical tickets"
Number Validations
Supported validations:
- Number greater than threshold
- Number less than threshold
- Number between (range)
- Number is not zero
Compatible field types:
Custom fields:
- Number Field (
float) - Any numeric custom field
Common use cases:
Story Points field:
Note: Story Points field has known platform limitations and is listed in "Not Supported Fields" section. If your Story Points field is working with Dynamic Screen Rules, you can apply number validations to it.
Use cases:
- Story Points quality gate (> 0, < 41)
- Budget thresholds (> $1000)
- Percentage validation (0-100 range)
- Prevent zero values
Example:
Field: Estimated Budget
Validation: Number greater than
Threshold: 0
Message: "Budget must be greater than 0 to ensure cost tracking"
Text Validations
Supported validations:
- Text minimum length
- Text maximum length
- Must contain text (substring)
- Must not contain text (substring)
Compatible field types:
System fields:
- Summary (
summary) - Description (
description) - ADF text extracted automatically
Custom fields:
- Text Field single-line (
textfield) - Paragraph multi-line (
textarea) - URL Field (
url)
Text extraction:
- Plain text fields: Character count includes all visible characters
- Rich text fields (Description): Text extracted from Atlassian Document Format (ADF), formatting ignored
- Whitespace-only text counts as length 0
Use cases:
- Incident summary quality (≥15 characters)
- Prevent TODO/TBD placeholders
- Require ticket references ("JIRA-" in summary)
- Enforce brevity (≤100 characters)
Example:
Field: Summary
Validation: Text minimum length
Length: 15
Message: "Summary must be at least 15 characters to ensure meaningful description"
Cross-Field Validations
Cross-field validations compare values between two fields to ensure consistency.
Supported validations:
- Date after another field
- Date before another field
Requirements:
- Both fields must be date fields
- Both fields must have values for validation to apply
- If comparison field is empty, validation passes (fail-safe behavior)
Common patterns:
| Target Field | Validation | Comparison Field | Use Case |
|---|---|---|---|
| End Date | Date after field | Start Date | Ensure valid timeline |
| Review Date | Date before field | Release Date | Review before release |
| Due Date | Date after field | Start Date | Due date after work begins |
| Resolution Date | Date after field | Created Date | Resolved after creation |
Example:
Field: End Date
Validation: Date after another field
Comparison: Start Date
Message: "End Date must be after Start Date to create a valid timeline"
Checking If Your Field Is Supported
Step 1: Identify your field type
- Go to Jira Settings → Issues → Custom Fields
- Find your field and note the "Type" column
Step 2: Match field type to this list
- System fields: Look in System Fields section by field name
- Custom fields: Match the type ID (e.g., "Select List (single choice)" =
select)
Step 3: Verify action support
- Check if the action you want to use is listed for that field type
- Special fields (select types) support Limit Options
- Date fields support Smart Values
- User fields support
currentUser()Smart Value
If your field isn't listed:
- Contact support with field type ID
- Check if it's a third-party custom field (may not be supported)
- Consider using a standard Jira field type instead
Related Pages
Actions documentation:
- Defining Actions - How to configure each action type
Smart Values:
- Using Smart Values - Date calculations and field references
Limitations:
- Screen-Specific Limitations - Which actions work on which screens
- Known Platform Limitations - Atlassian API constraints
Use cases:
- Limiting Dropdown Options - Examples using select fields
- Pre-filling Values - Examples using Smart Values
This list reflects currently supported field types and is updated as Atlassian adds new capabilities to the UI Modifications API.