What Fields Can I Map In My Jira Integration?
← Back to Jira section
Mapped fields
If a field is required in Jira and is presented in the Idea or User Story field mappings in the ProdPad integration set up, the field must be mapped to a ProdPad field.
- Pushing to development will error if a required field has not been mapped in the ProdPad integration configuration
- Pushing to development will error if the field has been mapped but the ProdPad field is empty. For example, Idea description is mapped to the Epic Summary and the Epic Summary is a required field, if a user pushes an idea without a description Jira will return an error
For fields to appear as an option in the Idea/User Story field mappings, the field must:
- Be added to a screen in Jira for the relevant issue type and the project the integration has been mapped.
- Can be required or optional
- The mapped data type must be compatible i.e. mapping a text field in ProdPad to an Attachment field in Jira will cause Jira to return an error. We recommend these being set to the default text renderer or the wiki-style renderer.
Required fields
Fields that are not mappable but need to be populated prior to issue creation must be set as ‘required’, part of a related screen and not set to ‘hide’ in the Jira field configuration. These can then be presented in the Push to Development slide out.
- If a field is not marked as required but is implemented as a validator on the create issue transition in a workflow the Jira will return an error when pushing to development.
- If the field is set to ‘hide’ in the field configuration, the field will not be pulled through into the ProdPad UI.
- Not all field types are supported, currently only user picker, single select fields (such as Components, Affected Version) and number fields
- Any required fields that use autocomplete or select list templates must have valid selectable options in the relevant project’s settings i.e. Components, Affected Version/s
| Jira Field Type | ProdPad Compatibility |
| Checkboxes | Partially supported - renders options as a single select list |
| Date Picker | Not currently supported |
| Date Time Picker | Not currently supported |
| Group Picker (mulitple) | Not currently supported |
| Group Picker (single) | Not currently supported |
| Labels | Mappable in integration set up when part of an issue screen |
| Number Field | Displays when made required - only single selection is supported |
| Paragraph | Mappable in integration set up when part of an issue screen |
| Radio Buttons | Partially supported - renders options as a single select list |
| Select List (cascading) | Displays on push when field is set as required and has valid options - only single selection is supported |
| Select List (multiple choice) | Displays on push when field is set as required and added to a screen in JIRA - only single selection is supported |
| Select List (single choice) | Displays on push when field is set as required and added to a screen in JIRA - only single selection is supported |
| Short text | Mappable in integration set up when part of an issue screen |
| User picker (multiple users) | Not yet supported |
| User picker (single users) | Not yet supported |
| Version Picker (multiple versions) | Displays on push when field is set as required and added to a screen in JIRA - only single selection is supported |
| Version Picker (single version) | Displays on push when field is set as required and added to a screen in JIRA |
If you would like to provide feedback on our JIRA integration or this document we would love to hear from you via our portal.