Hello,
With our current setup, we have a dedicated Slack channel where tickets from a specific project that are created with "Priority = Blocker" (highest priority level) are posted. This was configured through the Slack Integration page within the project in Jira. Pretty straightforward.
However, we noticed that tickets that are open in this project with a lower priority, but then escalated to a Blocker (after the ticket is already created), it will not post the ticket to the dedicated Slack channel. This is a pretty big gap in the integration given that we need to be made aware immediately in the Slack channel whenever any ticket is set to Blocker priority for incident management purposes.
I've checked other forums/answers highlighting the same issue, and I'm aware that there is a workaround involving going to Project Settings > Automation > Creating a New Rule. We'd like to avoid this solution given that it does not match the same notification "look" in the Slack channel.
Is there any way to set up the configuration so that, in this specific scenario (ie. a ticket in this project that has been escalated to Blocker priority after it has already been created), the jira automation posts the ticket link with high level details (as shown in the attached screenshot)?
Thank you!!
Yes, it's a big gap,
If you are open for 3rd party, you can do this via https://slackjira.com/. Works like a charm
Welcome to the Community!
If I did not get it wrong, here is what I'd do (at least start with)
You can customize the Automation rule to post to Slack in a way that slightly resembles the standard notification.
Automation > Create Rule and set up a Trigger with "Field value changed" for the "Priority" field. Add a condition to check if the new priority is "Blocker."
Then use the "Send Slack Message" action. and use the below code and smart values.
*{{issue.key}} {{issue.summary}}* has been escalated to Blocker.
Status: {{issue.status.name}}
Assignee: {{issue.assignee.displayName}}
Priority: {{issue.priority.name}}
Link: <{{issue.url}}|View Issue>
Like I said, it may be a good start to make it resemble a standard notification format.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.