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: Can we disable @mentioned_Users from issues that are created by automation?

Adrian Szubert

Hello Community!

As my question states - I have a few follow-up tasks created automatically whenever a story reaches a specific status in the Workflow.

If we tag a User in Story, it will automatically tag them in the follow-up story.

It is quite annoying whenever the Product Owner or Business Process Owner is flooded with dozens of notifications on issues that are irrelevant to them at this stage.

Is there any way we can switch it off?

Best regards,

Adrian

Accepted answers

Bill Sheboy

Hi @Adrian Szubert

If you look at the markup for a mention with Jira Cloud, it looks like this:

[~accountid:userAccountId]

And so in your rule that clone / reuse such descriptions, the rule could replace those using text functions, such as replaceAll() with a regular expression: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#replaceAll-String-regex--String-replacement-

For example:

{{issue.description.replaceAll("(\[~accountid:.+\])", " MENTION_REMOVED ")}}

If you want to replace the user-mention with their display name, I believe that is more challenging, and may only be possible if you have a limited number of users to handle.

Kind regards,
Bill

All comments

Marc -Devoteam-

Hi @Adrian Szubert

Are they the reporter of the follow-up stories or are they stated as watchers or are the issue linked or is it in the workflow, what is the case?

What kind of notifications are they getting?

Also what does the automation look like, is it somewhere in the automation that they are related to the follow-up stories

Adrian Szubert

Hey @Marc -Devoteam-

No, they are just mentioned in the story's description, and the description (along with other fields) is cloned to the follow-up task - either QA Task or Smoke Test Task.

The tagging I mean is same as I mentioned you above - @UserName

Marc -Devoteam-

Hi @Adrian Szubert

Can you show example issues, as notification are triggered via email or as user being assignee, reporter or watcher.

@mention is a single notification, cloning via cloning option or via an automation rule should not keep @mentioned user notified.

What kind of notifications are the @mentioned users getting?

Adrian Szubert

Hi @Marc -Devoteam-

It can be problematic to share those, without sharing some more confidential details.

What I can tell is that users are receiving Email notifications from the Automation User (as the Automation User is used for that).

It is exactly as mentioned, the User is mentioned in the Parent in the description field, cloning that field to a new story, and keeps sending those email notifications (also ring bells in JIRA itself).

Bill Sheboy

Hi @Adrian Szubert

If you look at the markup for a mention with Jira Cloud, it looks like this:

[~accountid:userAccountId]

For example:

{{issue.description.replaceAll("(\[~accountid:.+\])", " MENTION_REMOVED ")}}

If you want to replace the user-mention with their display name, I believe that is more challenging, and may only be possible if you have a limited number of users to handle.

Kind regards,
Bill

Adrian Szubert

It works great! Thanks @Bill Sheboy

How would you approach "keeping" the name of the tagged User? As you mentioned, it is hard, but I wonder how that would look like

Bill Sheboy

Backing up a bit...as something appears to have changed since the last time I tried this scenario a few years ago. Now this:

{{issue.description.text}}

Will lookup and replace the mentions with the users' display names. However that will also remove all formatting from the field. If you need to preserve the formatting...

Let's assume you only had a few users in your site / project. In that case, you could chain together replacements. This would work (and be very slow) for up to a few dozen users.

{{issue.description.replace("[~accountid:1234]", "Alice").replace("[~accountid:5678]", "Bob").replace("[~accountid:9801]", "Mallory")}}

Messy, redundant, brittle, difficult to maintain, and effective.

If you had up to 200 users, you could use a quite complicated approach using list iteration, lookup tables, and text functions. I have not tried that for this scenario and would need to actually build the rule to confirm it works as expected.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud