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

Automation for adding labels when user replies to tickets.

Theodoros Karipidis

Hi team,

We were investigating a way to have a queue with the "to do" tasks concentrated for our agents.

We came up with an automation, which will add a specific label to the ticket, every time that a customer will add a comment.
And when the assignee replies back, the automation will remove that label.
After that we set a personalised queue for the agents, and in general it worked pretty well.

But we face only issue.
The automation is using, lets say, "atlassian.bot" user as actor.
And when a change is done from that actor, "a label is added"/"a label is removed", that will pop up in the bell notification, which will result in a massive/useless amount of notifications, to the point that the agents can not longer properly track the important notifications.

My question here is... which is the best way to filter out those notifications?

Keep in mind that we do need to use the bell notif. area, since the agents can get notified for mentions, tags, etc.

Comments

Martin Bayer _MoroSystems_ s_r_o__

Hi @Theodoros Karipidis , if you're using Edit action, there is an option to disable notification. DId you try it?

Theodoros Karipidis

Hey Martin,

Thank you for your reply.

That is already deactivated for all actions in the automation rule.
I have a feeling that this is coming from the Jira notification side, instead of the automation.

I just have no idea where to look for it.

I even try to create a rule (Project settings -> Notifications), to block all notifications from that specific user, which also did not work.

Daniel Ebers

Hi @Theodoros Karipidis

if I understand you correctly Automation is setting and removing labels, perhaps alongside with other desired actions that are required for your teams.

At least setting and removing labels trigger, from what I know, an "Issue Updated" Event.

This event then leads to have an email send - namely where your notification scheme it says it should go to.

So, from the last occurrence here in Community you would have to inspect your Notification Schemes but I am not aware of any option to say "when Automation updates the label, please be quiet, in other cases send the mail".

Configure notification schemes
https://support.atlassian.com/jira-cloud-administration/docs/configure-notification-schemes/

Regards,
Daniel

Theodoros Karipidis

In the Notification Scheme -> Issue Updated, I see an option to block all messages from a specified user.

Based on that is it safe to assume that I can block ALL notifications from the "jira.bot" user (which is also the automation actor)?

I am trying to find at least a work around, since as it is, the bell notification icon is pretty much useless, since it has +3 notifications for every action taken, and as a result we lose the actual meaningful notifications.

Thorsten Letschert _Decadis AG_

Hi @Theodoros Karipidis ,

Unfortunately, this looks like some has added a custom event called 'Disable Notifications' to your event list (accessible via %yourSiteURL%.atlassian.net/secure/admin/ListEventTypes.jspa).

That said, you can't block the notifications with that configuration, but you are in fact sending a notification to the jira bot user, when the custom event is triggered.

Theodoros Karipidis

@Thorsten Letschert _Decadis AG_ that is correct.

The person that set up this project probably created this as well:

But when I see that, it gives me the impression that what I am trying to do, is in fact possible.
I just can't figure a way to actually do it.
(yea... I am pretty new in the whole Jira universe)

Do you have any suggestions?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

new-to-jsm