nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation for When a deployment to Production succeeds → Then Release version runs

unknown

We have an automation to run When a deployment to Production succeeds → then release version, If we have 10 tickets tied to release then the automation runs 10 times. And another automation to trigger mail and teams notification about the release which is also running 10 times and 10 email and 10 messages triggered.

How to restrict this to run the notification only once?

Accepted answers

All comments

Bill Sheboy

Hi @[deleted]

For a question like this, I recommend posting images of your complete rules and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions.

Until we see those...

As you have learned, some of those DevOps triggers fire for each issue, which is unhelpful when you want to send one notification (e.g., email and message) about the results/progress.

One way to mitigate this is to add conditions to your second rule such that the notification only sends after the last item is updated. You do not indicate the trigger for your second rule. Let's assume it is issue transitioned. For example...

First rule:

triggered deployment to Production,
releases the version, and
transitions the issue to some status

Second rule

triggered on issue transition
sends email
sends message

You could modify your second rule as follows to send only one notification

triggered on issue transition
using a JQL condition, or lookup issues and advanced comparison, confirm that all the issues in the version (for the trigger issue) are in the same, expected status
use lookup issues to gather the issues
send an email with all the issues referenced in the lookup

Kind regards,
Bill

Shalini Saravanan

When we add a condition to release the version(Status!=Released), automation not running and throwing the below error Screenshot 2023-07-06 at 9.24.44 PM.png

Bill Sheboy

Reviewing the audit log, it appears your release names have non-alphanumeric characters in them. Please try wrapping the smart value in quotation marks to make that work.

Also...do you want that condition in both this rule and the second one? The first does the version release and the second rule does the email, correct?

Shalini Saravanan

Do you mean,currently condition added as project = ACU AND fixVersion = {{issue.fixVersions.first.name}} AND (Status != Released).

Update with quotes like --> project = ACU AND fixVersion = "{{issue.fixVersions.first.name}}" AND (Status != Released)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud