With FlowEQ's Jira integration, you can create Bugs, Tasks, and Issues in your Jira instance without your team ever leaving the support ticket. You can create your own templates and ensure your team follows them before the Jira ticket is filed. Data can also pass into JIRA from the ticket or case fields automatically
How to use the Jira integration
In Flow Builder, add a new step type and select the Jira: Create New Issue steptype.
Title
Summarize what you want your team to do when they reach this step. Keep it short and sweet as it will appear up top where space is limited.
Automatically run when step launched?
Check this box if you want this step to create Jira tickets all on it's own, though we advise against this as you'll likely need at least some details from your team.
Project Name
Select the Jira project you would like this new issue to be filed within. This is required.
Issue Type
Select the type of ticket you'd like your team to create from Task, Bug, or Story. This is required.
Issue Summary
If you want to write a phrase or template you'd like the Jira ticket to be titled with, enter it here. You can also use the ➕ button to automatically pull in variables from your CRM or Workboard fields, such as the ticket ID or an error code.
Issue Description
Write the template description the Jira ticket should have. You can write as little or as much as you like. We recommend adding text asking for each detail you'd like your team to describe. Again, your can also use the ➕ button to automatically pull in variables from your CRM or Workboard ticket fields.
Populate Ticket Fields
Here you can click "Add New Field", select a field in Jira and write to it from your CRM. Again, you can also use the ➕ button to automatically pull in variables from your CRM or Workboard ticket fields. This is especially handy if your CRM and Jira fields match up - as you can directly read data from your CRM and write it to Jira.
Paragraph fields
If you have paragraph fields configured in your Jira instance, you can also enter text for them here.
Comments
0 comments
Article is closed for comments.