The obvious improvement would be converting the form directly into a JIRA ticket, but I’m not sure how to do that whilst also ensuring potential bugs are triaged / discussed first.īesides that, in the shorter term a couple of simple changes can make the process smoother: Whilst this setup is an improvement over our former process (or no process!), it’s definitely not perfect. Don’t forget to disable the message sending in the “Open a form” step, or the results will be sent twice!Īll done! Anyone submitting the bug report form should now see the data posted in the Slack channel, where it can be triaged easily. All the variables are easy to access, including metadata such as who submitted the form. We now have to essentially recreate the previous message. Open up your workflow’s settings, and click “Add step” at the bottom. ![]() Instead of sending the form results directly into the channel, we are going to send a separate message, using the received values: Instructions To fix this, we need to change our workflow. The output is all combined into one line, making it essentially unreadable even for short forms: If you try using Jira’s create ticket functionality from the form results, you may notice something… not great. Now, whenever somebody fills in the form, a message is sent to the channel. Here’s a summary of the simple bug reporting workflow we’ve just created.Īnd here’s how it can be used, by clicking the “+” under the message box and selecting the workflow. The actual fields you need will vary massively, but using your Jira ticket’s fields is the easiest place to start.įor now, just send the form output to the channel. Open up the settings for the channel you want bugs to be reported in, then “Add a workflow” under “Integrations”.Ĭreate your form. This can include simple things like a description of the bug, or a multiple choice dropdown asking the bug’s severity. Next, we want a form that colleagues can fill in to give us any information we need. You now have the ability to create tickets from any message! The Jira bot should have posted in the connected channel. This is only used for optional new ticket notifications, so doesn’t matter much. Provide Jira access to your workspace (this may require approval from your Slack administrator) Within your Jira project’s settings, navigate to the built-in “Slack integration” tab and click “Connect to Slack”. Both Slack and Jira officially support connections to each other, so this process is straightforward. Once connected, you will be able to make Jira tickets from any Slack message, as well as receive updates for new tickets, updated tickets, etc. The form’s fields don’t prefill the Jira form, and require copying from the description during ticket creation.The “workflow” feature used for the form requires a paid Slack plan.There are a couple of important caveats with this method, that are worth considering before implementing: Send this bug report form’s information to Jira.To make this approach, we’re going to need to achieve 2 main tasks: ![]() Additionally, any follow-up questions can be asked directly to the bug submitter, avoiding any low quality / out of scope / duplicate bugs unexpectedly appearing in the backlog. ![]() This semi-automated approach makes the process easier for the engineers / whoever is triaging the reports, by ensuring all the relevant information is provided upfront, and letting it be actioned without leaving Slack. ![]() Just as importantly, they can also add any relevant photos / videos / files, and answer any questions the triaging engineer might have whilst trying to reproduce the issue. As all the actions are public, the submitter can easily keep track of any bugs they want to follow the progress of, whilst also being confident that their report has been acted on. The workflow aims to reduce the friction colleagues may face when raising bugs. Here’s how to implement something similar. To ensure sufficient detail, we use a Slack workflow to standardise bug reporting and simplify Jira ticket raising. Like many engineering teams, the Photobox app team lets colleagues from other departments report bugs internally via Slack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |