- Get started
- About
- Supported fields
- Migration to Cloud
- User's guide
- Customer's view
- Configuration
- General Configuration
- Scopes
- Fields configuration
- Filters management
Supported fields and third-party app support
Here you can find a comprehensive list of fields supported by My Request Extension
Supported fields/custom fields
Field | Columns | Criteria |
---|---|---|
Summary | Yes | Only with a search bar |
Key | Yes | Only with a search bar |
Project | Yes | Yes |
Status | Yes | Yes |
Description | Yes | Only with a search bar |
Priority | Yes | Yes |
Labels | Yes | Yes |
Labels (custom field) | Yes | Yes |
Fix Version/s | Yes | Yes |
Affects Version/s | Yes | Yes |
Due Date | Yes | Yes |
Resolved (Resolution Date) | Yes | Yes |
Resolution | Yes | Yes |
Created | Yes | Yes |
Updated | Yes | Yes |
Assignee | Yes | Yes |
Reporter | Yes | Yes |
Request participants | Yes | No |
User Picker (single user) | Yes | Yes |
User Picker (multiple users) | Yes | Yes |
Linked Issues | Yes | Yes |
Comment (including internal comments) | No | Yes |
Select List (single choice) | Yes | Yes (including disabled options) |
Select List (cascading) | Yes | Yes |
Select List (multiple choices) | Yes | Yes (including disabled options) |
Checkboxes | Yes | Yes (including disabled options) |
Radio buttons | Yes | Yes (including disabled options) |
Organizations | Yes | Yes |
Text Field (single line) | Yes | Yes |
Text Field (read only) | Yes | Yes |
Text Field (multi-line) | Yes | Yes |
Number | Yes | Yes |
Date Time Picker | Yes | Yes |
Date Picker | Yes | Yes |
Component/s | Yes | Yes |
Time Spent | Yes | No |
Original Estimate | Yes | No |
Σ Original Estimate (aggregate) | Yes | No |
Remaining Estimate | Yes | No |
Σ Remaining Estimate (aggregate) | Yes | No |
Time Spent | Yes | No |
Σ Time Spent (aggregate) | Yes | No |
SLA* | Yes | No |
Type (customer request type) | Yes | Yes |
Epic Link | Yes | Yes |
Issue Type | Yes | Yes |
Votes | Yes | No |
URL Field | Yes | Yes |
*The support for SLA includes all the SLA custom field types, such as: Time to first response, Time to resolution, Time to close after resolution etc. Note that you can create a custom SLA by accessing the Project Settings > SLAs.
Keep in mind, that using the Epic Link field, as a column or in criteria, might cause a slightly longer loading time of the Requests screen if many requests are to be displayed.
It is due to security reasons, where not all existing Epic Links are considered during filtering, but only those that the customer has access to.
For example, the entire Jira instance has 3 Epic Links: XYZ, ABC and 123. The customer only has access to requests which regard Epic Links XYZ and 123. Therefore, in the criteria section, there will be only XYZ and 123 options visible.
Third-Party App Support
Field | Columns | Criteria |
---|---|---|
Rich Text Editor from Extension | Yes | No |
Bundled Fields from Extension | Yes | Yes |
Dynamic Cascading Select from Dynamic Forms | Yes | No |
Dynamic Checkboxes from Dynamic Forms | Yes | No |
Dynamic Multiselect from Dynamic Forms | Yes | No |
Dynamic Radio Buttons from Dynamic Forms | Yes | No |
Dynamic Select from Dynamic Forms | Yes | No |
Secured Multiselect from Dynamic Forms | Yes | No |
Secured Select from Dynamic Forms | Yes | No |
Live Text from Elements Connect | Yes | No |
Assets objects from Assets | Yes | Yes |
Assets referenced objects from Assets | Yes | Yes |
Account from Tempo | Yes | No |
SLA PowerBox | Yes | No |
Issue(s) Picker from ScriptRunner | Yes | Yes |
Custom Script Fields from ScriptRunner | Yes | Yes |
Issue Picker Custom Field from Teamworkx Issue Picker | Yes | Yes |
CRM Company from CRM for Jira | Yes | No |
Calculated Date-Time Field from Jira Workflow Toolbox | Yes | No |
Calculated Number Field from Jira Workflow Toolbox | Yes | No |
Calculated Text Fields from Jira Workflow Toolbox | Yes | No |
SumUp Calculated Field from sumUp for Jira | Yes | No |
SumUp Progress Field from sumUp for Jira | Yes | No |
- In order for the Assets objects custom field to work as criteria, you need to allow your customers to select the field objects. Learn more by following the Enable access for customers instructions.
- Due to API limitations, when Assets objects custom fields are added as criteria, they will not respect the following Scope configuration: Object Schema, Filter Scope (IQL), Filter Issue Scope (IQL), Filter Assign Scope (IQL) and Make Filter Assign Strict.
In the Teamworkx Issue Picker Custom Field preferences, My Requests Extension does not take Display Attributes settings into account.
If you can’t find the answer you need in our documentation, raise a support request.