- Get started
- About
- Conditions and validators comparison
- Migration to Cloud
- Connect to Assets API
- Use cases
- Dynamic Forms
- Dynamic Forms Overview
- Add Dynamic Fields
- Add Translations
- Configure Conditions
- Configure Validators
- Copy Dynamic Fields
- Display Dynamic Fields
- Dynamic Fields in Team-managed projects
- REST API
- Use Case
- Supported fields
- Bundled Fields
- Bundled Fields Overview
- Global Configuration
- Project Configuration
- Display Bundled Fields
- Search with Bundled Fields
- Automation
- Request details view
- Customization Overview
- Display Additional Details
- Display Attachments
- Display Related Issues
- Display SLAs
- Use Case
Conditions and validators comparison
Learn about Conditions and Validators by comparing Extension Forms with the native Jira Forms
When it comes to the customization of Forms, Extension for Jira Service Management offers a variety of conditions and validators. Below you can learn about a comparison regarding the native Jira Forms and Extension Forms.
Conditions
Jira Forms | Extension Forms |
---|---|
Sections can be displayed as always or conditionally, based on the selected options. | Fields are displayed dynamically based on various conditions selected by the user. |
For more information about configuring Conditions in the Extension app, see Configure Conditions.
Validators
Validators | Jira Forms | Extension Forms |
||
---|---|---|---|---|
Text fields | ||||
Short text | Response required | |||
Must match regex pattern | soon | |||
Minimum | characters | |||
words | soon | |||
Maximum | characters | |||
words | soon | |||
Contains | ||||
Is URL address | ||||
Is email | ||||
Long text | Response required | |||
Must match regex pattern | soon | |||
Minimum | characters | |||
words | soon | |||
Maximum | characters | soon | ||
words | soon | |||
Contains | ||||
Paragraph | Response required | |||
Minimum | characters | soon | ||
words | ||||
Maximum | characters | soon | ||
words | soon | |||
Contains | ||||
Response required | such custom field doesn’t exist | |||
Minimum | characters | such custom field doesn’t exist | ||
words | such custom field doesn’t exist | |||
Maximum | characters | such custom field doesn’t exist | ||
words | such custom field doesn’t exist | |||
URL | Response required | |||
Minimum | characters | soon | ||
words | soon | |||
Maximum | characters | soon | ||
words | soon | |||
Contains | ||||
Choice fields | ||||
Radio buttons (single choice) | Response required | |||
Required choice | ||||
Checkboxes (multiple choices) | Response required | |||
Required choice | soon | |||
Minimum number of choices | ||||
Maximum number of choices | ||||
Dropdown (single choice) | Response required | |||
Required choice | ||||
Multiselect dropdown (multiple choices) | Response required | |||
Required choice | soon | |||
Minimum number of choices | ||||
Maximum number of choices | ||||
Select list (cascading) | Response required | |||
Is child required | ||||
Date fields | ||||
Date | Response required | |||
Earliest date | ||||
Latest date | ||||
Is after request creation (+/- offset) |
+/- minutes / hours/ days / weeks / months / years | |||
Is before request creation (+/- offset) | +/- minutes / hours/ days / weeks / months / years | |||
Date & Time | Response required | |||
Earliest date & time | ||||
Latest date & time | ||||
Is after request creation (+/- offset) |
+/- minutes / hours/ days / weeks / months / years | |||
Is before request creation (+/- offset) | +/- minutes / hours/ days / weeks / months / years | |||
Time | Response required | such custom field doesn’t exist | ||
Earliest time | such custom field doesn’t exist | |||
Latest time | such custom field doesn’t exist | |||
Numeric fields | ||||
Number | Response required | |||
Minimum | ||||
Maximum | ||||
Whole numbers only | soon | |||
Is integer | ||||
User fields | ||||
Single user | Response required | |||
Multiple users | Response required | |||
Other fields | ||||
Attachment | Response required | |||
Size less than (kB) | ||||
Assets | Response required | |||
Minimum number of objects | ||||
Maximum number of objects |
Bear in mind that in order to use Assets in Jira Service Management it’s required to upgrade to the Premium Plan and establish your connection with the Assets API. To learn more, navigate to the Connect to Assets API section.
If you can’t find the answer you need in our documentation, raise
a support request.
Include as much information as possible to help our support team resolve your issue faster.