zAgileConnect Flow Action - Create Issue v2
You can create an Issue by using Salesforce Flow and adding the “Create Issue v2“ action to your flow. The action has the following fields:
Create Issue v2 Action Fields
Field | Type | Required | Description |
|---|---|---|---|
Create Metadata |
| The metadata information necessary for creating a Jira Issue. It can be retrieved using the zAgileConnect Flow Action - Get Issue Create Metadata | |
Record Id | String |
| The Salesforce record Id to link to the new Jira Issue. |
Summary | String |
| A brief one-line summary of the Issue. |
Description | String | A detailed description of the Issue. | |
Environment | String | The hardware or software environment to which the Issue relates. | |
Labels | String [] | Labels to which this Issue relates. | |
Priority | String | The importance of the Issue in relation to other issues (e.g. High, Low, Lowest). | |
Due Date | Date | The date by which this Issue is scheduled to be completed. | |
Affects Versions | String [] | Project versions for which the Issue is (or was) manifesting. | |
Fix Versions | String [] | Project versions in which the Issue was (or will be) fixed. | |
Components | String [] | Project components to which this Issue relates. | |
Reporter | The Jira account who entered the Issue into the system, use the zAgileConnect Flow Action - Find Jira Users to retrieve a Jira user account from username, display name or email. Leave blank to use the Jira account associated with the current Salesforce user (if the current Salesforce user had previously authenticated to Jira directly, otherwise it will be the Jira Integration User account) | ||
Assignee | The Jira account whom the Issue will be assigned, use the zAgileConnect Flow Action - Find Jira Users to retrieve a Jira user account from username, display name or email. Leave blank to let Jira auto assign the Issue. | ||
Issue Link | The Issue Link to another Issue. For example “relates to“, “duplicated by”. | ||
Security | String | The Security Level for the Jira Issue. | |
Time Tracking | The original and remaining time estimates for resolving the Issue. | ||
Custom Fields | The list of custom fields, it accepts a list of ZFlowCustomField apex objects. | ||
Raw JSON Fields | String | [Optional] Use this input to set Jira Standard or Custom Fields for types that are not supported by zAgileConnect. This input accepts a JSON Object where each attribute represents a field. The expected JSON format for each field type is defined by the Jira Rest API for creating Issues. | |
Sanitize Fields | Boolean | When set to true, it ignores passed Issue fields that do not match the Create Issue Screen fields defined in Jira. |
Create Issue v2 Output Fields
Output | Type | Description |
|---|---|---|
Error Messages | String [] | A list of error messages associated with the Jira Issue creation. |
Has Error | Boolean | Indicates whether there is an error related to the Jira Issue creation. |
Issue Id | String | The Issue Id of the new Jira Issue. |
Issue Key | String | The Issue Key of the new Jira Issue. |
Issue Url | String | The Issue URL of the new Jira Issue. |
Record Id | String | The Salesforce record Id that was linked to the new Jira Issue. |
This action makes callouts to Jira and so when using it from “Record Triggered Flows“ make sure to use it from within an Asynchronous Path.
Setting Custom Fields Data
Jira Issue custom fields can be set using the Custom Fields field. This fields expects a collection of ZFlowCustomField, for each Jira type of custom field there is corresponding Apex-Defined class. One required field to build a custom field variable in the flow is the custom field Id (starts with customfield_). To find the custom field Ids use the following REST API provided by Atlassian:
Create meta for Jira Cloud
https://{jiraBaseUrl}/rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}Create meta for Jira Server or Data Center
https://{jiraBaseUrl}/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}
Replace {jiraBaseURL}, {projectIdOrKey} and {issueTypeId}, to find the Issue Type Id see Finding the ID for Issue Types.
for example https://example.atlassian.net//rest/api/3/issue/createmeta/SFTEST/issuetypes/1 will produce:
Find the metadata for the custom field by name (Product Code in the example above) in the response.
To set custom field values in the Flow you need to create a collection variable of type ZFlowCustomField.
Then create a variable for each custom field (an Apex-Defined variable resource of the desired type), for example for a text custom field:
Use the Assignment element in the flow to set the custom field Id and the value as in (1) in the screenshot below, and add the field reference to the collection of custom fields (2)
Finally, the CustomFields collection can be passed to the Create Issue v2 Flow Action. For more information on the types of custom fields supported and its attributes see ZFlowCustomField.