Respond to a Bug Report
Responding to bug reports is an essential part of support and improvement processes, and solutions should come as quickly as possible. This workflow template allows you to use specific emojis to tag posts in Slack for which you want to automatically create a Jira ticket by simply using an emoji reaction on the post. The template has defined the issue-type as Bug, but you can change the issue-type if you like.
Customizing the Respond to a Bug Report Workflow
After you download and import the template, fine-tune the workflow by evaluating and making adjustments to each step. You'll likely need to make some changes to perfect the workflow for your specific use by, for example, selecting a Slack channel for the workflow, choosing a Jira project, personalizing the text your coworkers will see, etc.
The template is best viewed as a head-start rather than a complete, ready-to-use workflow. Add a little personal spice and make it your own!
With the template imported, open the workflow so all the steps are visible.
If you just imported the template, the steps may already be visible. If they aren't, click Respond to a Bug Report - Template on the Your Workflows tab.
If you renamed the workflow when you imported the template, click the new title.
Click Edit next to each template step to review and update the contents (if necessary).
Here's a summary of each step in the workflow and details you may want to customize:
Emoji Reaction Workflow Trigger
This template uses an emoji reaction to initiate the workflow. Select the channel in which you want the workflow to exist, then select the emoji you want to trigger the workflow.
Extract Slack Message Content
Leave this step as-is for this specific template. Basically, it defines the Slack messages you add an emoji reaction to as the asset Jira is to extract and use to create a Jira issue (in the next step of the workflow).
In order for the app to retrieve the message content from Jira, it must be a member of the target channel; add it by typing
@Workflow Steps for Jirain the channel. Otherwise, the step will fail.
Create Jira Issue
Edit this step to select your desired Jira instance and project in which the new bug is to be created.
The template has a predefined summary, which includes a variable for the name of the person who sent the original message (or in this case, the person who used the emoji).
Most of the fields on this step are optional. Make it work for your project.
Prompt for Jira Fields
This step allows you to share field values between Jira and Slack. Available Jira fields include Jira Username, Project Name, Issue Type, Created Issue Key, Summary, and more.
The message sent to the Slack user is optional. Update it to better suit your project, if you like.
Update Jira Issue
This step declares the type of update you want to make to the Jira issue (comment, status, or assignee), and it allows you to define the Jira issue to be updated.
As noted in the dialog, it's very useful to use this step in conjunction with the Prompt for Jira Fields step, so Jira values can be inserted as variables.
Send a Message
This step contains the message to be sent to the bug reporter.
Review the default message, and customize it to best fit your workflow needs.
- When you're finished fine-tuning the template, click Publish Changes at the top-right of the dialog.
- Test the workflow in Slack!
It's always best to test the workflow before introducing it to your coworkers. Ensure that the steps are pulling the right info from Jira and working as you'd expect them to.