Hello. My team has a private Slack channel where we report our tasks. I would like to automate the following process:
1. When somebody report a task (the report always has the same structure), I'd like to automate the transition the ticket statuses in Jira (for example, To Do --> In progress) and the report this change in the corresponding thread.
2. When somebody review the task in Slack and provide feedback in the thread, we usually finishes with a keyword. Then I'd like to change the ticket status automatically in Jira again.
Is it possible with Slack and Jira integration? Do I need some third party? Thanks for the help.
Hey @Jean Paul Piedrahita Garcia
When you mention 'someone reporting a task in Slack,' are you referring to creating a new work item directly from Slack? If so, you can utilize the 'Issue created/updated' trigger in Jira automation. The same principle applies when someone reviews a task in Slack.
Both actions will be captured by Jira, allowing the 'issues created/updated' trigger to function effectively. To distinguish between issues created via Slack and those created directly in Jira, you can incorporate a specific keyword in the description, summary, or another field as part of the rule.
Please check the below rule:
The trigger is set to activate when the summary value changes upon issue creation or editing (since the summary field is mandatory for creating an issue, it serves as a reliable trigger). You can adapt this by choosing a different field for editing, such as a comment.
The rule checks if the summary contains a specific keyword, like '-xyz,' to differentiate issues created through Slack from those in Jira. If all issues from Slack are created within a single project, you can configure the rule for that project alone, eliminating the need for this condition.
As an action, you can set a transition. Additionally, you can use 'if-else' conditions to tailor the workflow: for instance, if the description contains 'xyz', transition to Status A; if the description contains 'xyz' and a comment includes 'abc'(for the second requirement), transition to Status B. This approach works for both issue created and edited
I hope this helps. But if I did not understand your requirement correctly, please correct me so I can assist you better.
Thanks :)
Thank you for your response. I just got permissions to access Jira Automations, as I couldn't before. Maybe I wasn't a bit explicit. The dynamics we employ is as follows:
(Assuming the ticket is already created previously).
1. Once the work is completed, the person reports in Slack with the example structure "XYX-123, considerations, file".
2. Jira should detect this message and change the status of the XYX-123 ticket from To Do or In progress to QA.
3. Jira sends a message in the Slack message thread, advising of the status change.
4. A person makes comments in that Thread as feedback. When finished, it sends a message with a keyword such as "XYX-123 - finalize revision".
5. Jira detects the message and changes the QA status to in progress.
6. Jira sends a message in the Slack message Thread, notifying of the status change.
All is this possible with your solution? Or should I consider something else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Jean Paul Piedrahita Garcia ,
Yes, the solution I provided will work for your requirement.
You can configure your project to include/exclude issue events from slack notifications, so you can get slack notifications for issue edited/comments added etc
For the automation triggers you can use, issue edited/comments as well. So please try this solution. It should work if everything is set correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mayura Gautham .
I will try this, thank you. I have a question: since I want the Jira issue to change the status automatically based on an external call from Slack, could the trigger here in Jira be applied directly? Or are these triggers only used to send messages to Slack?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Jean Paul Piedrahita Garcia
For your requirement, the only way to connect with Slack is to use an automation rule action, which is limited to sending a Slack message.
The Rule trigger could be any change made to the issue; regardless of whether the change is made via Slack or Jira, the rule will trigger.
Also, please do accept my answer if you think this would work for you :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.