Project Key
field) and select the Issue Type
to create the ticket in.
This workflow action can be used to create Jira tickets for either incidents or action items. It is recommended that you use the Create Jira Subtask for action items. However, if your project teams don’t use subtasks, you can use this action to create Jira issues as well.
Jira Issue to Update
field using the {{ incident.jira_issue_id }}
variable.
Parent Jira Issue
field using the {{ incident.jira_issue_id }}
variable. The Project Key
entered here must be the same as the one used in the original Create Jira Issue action.
This workflow action is intended to be used for action items or sub-incidents.
Team
, but it’s stored as a “custom field”. In addition, it only allows a single team to be selected. To map to this field in Jira, you’ll need to use the following syntax format:
Default
tabs in each of the above workflow actions will allow you to set default Jira fields. If you have custom fields defined in your Jira project or would like to dynamically set Jira fields, you will need to do so via custom mapping in the Advanced
tab.
Custom Fields Mapping
field in the Advance
configuration tab.
In order to map to custom fields in Jira you would need to know the following information:
Error | Comment |
---|---|
issue_id cannot be null. | Reason for error… This often happens on Update Jira Issue action. This means the reference Jira issue you’re attempting to update does not exist. How to fix… Ensure your workflow does not run until AFTER a Jira issue has already been created and linked to the incident. |
"customfield_12345": "Custom Field is required." | Reason for error… This means the specified custom field is configured as a required field in the Jira project and your workflow isn’t passing it any value. How to fix… You can either add custom fields mapping to map to the specific field or configure the Jira project to make the field optional. |
unexpected token at '{ "customfield_10032": }' | Reason for error… Your custom mapping syntax is incorrect. How to fix… Correct your mapping syntax. |
Specify a valid project ID or key | Reason for error… This means the Jira Project Key you’ve selected in the action is not available in the selected Jira instance. How to fix… Reselect the Jira Instance and then reselect the Project Key. |
The issue type selected is invalid. | Reason for error… This means the Jira Issue Type you’ve selected in the action is not available in the selected Jira project. How to fix… Reselect the Project Key and then reselect the Issue Type. |