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; } } }

Using trigger "When: Pull request created" how can you run the rule only once for multiple issues

Marc-André_s2k8t2

In Jira Automation when using the When: Pull request created I typically have an Issue fields condition step that checks for a Component field value and then post a message to Microsoft Teams.

The issue I'm facing is that if the pull request in question contains more than one issue it will post multiple messages to teams, one for each issue in the pull request.

Is there a way of validating the component of either all or the first issue in the pull request and proceed to only post a single message to Microsoft Teams.

Thanks!

Accepted answers

Bill Sheboy

Hi @Marc-André

Full disclosure: I am not actively using the DevOps triggers at this time, and based on what I understand about them, I wonder if you could...

When the pull request trigger fires the rule, it has the {{pullRequest.title}}
As you note the title contains multiple issues, you could parse those issue keys out using the text functions and RegEx
Then pick one of them (e.g. first) to get the sampled key
Use an Advanced Compare Condition to prevent a loop, only proceeding if the trigger Issue key matches the sampled key
Log your message to Microsoft team

Best regards,

Bill

All comments

Marc-André_s2k8t2

Good to know.

Bill Sheboy

Hi @Marc-André

Full disclosure: I am not actively using the DevOps triggers at this time, and based on what I understand about them, I wonder if you could...

When the pull request trigger fires the rule, it has the {{pullRequest.title}}
As you note the title contains multiple issues, you could parse those issue keys out using the text functions and RegEx
Then pick one of them (e.g. first) to get the sampled key
Use an Advanced Compare Condition to prevent a loop, only proceeding if the trigger Issue key matches the sampled key
Log your message to Microsoft team

Best regards,

Bill

Marc-André_s2k8t2

Hi @Bill Sheboy

Thank you for your answer. Although a bit more complex than I expected this automation to be this does solve my issue.

We might miss some PRs or get invalid notifications if a user does not name the PR appropriately but in the end this greatly eliminate notification spam.

Lets hope the values contained in the pullRequest payload gets expanded a bit in the future.

Best regards,

Mark

Bill Sheboy

Mark, you may also want to search in the Code Barrel (now part of Atlassian) backlog to see when they might improve this area in triggers. Unfortunately we cannot vote for/watch issues in this backlog.

https://codebarrel.atlassian.net/issues/?jql=project %3D AUT AND resolution %3D Unresolved ORDER BY Key DESC&startIndex=50

Best regards,

Bill

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