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 rule to unwatch the issue

Alexey_gudeo1

Greetings, i have a request from a project manager to create an automation based on CRON with a action 'comment'.

An actor for that comment will be real person (user_id).

Problem - that action triggers 'auto-watch' feature, which is turn on in that user personal settings, and their willing to keep it like that.

But that automation leads to overwhelming stream of notifications and emails.

Question, is it possible to add to that automation 'un-watch' step? or any other way to reduce unwanted noise

Accepted answers

Trudy P Claspill

Hello @Alexey

Yes, there is a Manage Watchers action.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Manage-watchers

You would want to use the Re-fetch action after the Comment action to ensure you get the updated issue after the user has been added as a Watcher because of the comment addition. Then you could add the Manage Watchers action to remove the comment author from Watchers.

All comments

Trudy P Claspill

Hello @Alexey

Yes, there is a Manage Watchers action.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Manage-watchers

Alexey_gudeo1

@Trudy P Claspill perfect, thanks.

Alexey_gudeo1

UPDATE:

It works great then paired with IF advanced compare values like {{issue.watchers}} to make a check BEFORE adding a comment to see if a person actually was a watcher before the automation, to prevent accidental unwatch.

The rule looks like:

IF person is not watcher

THEN add comment, re-fetch and unwatch

ELSE add comment

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

automation