It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to ignore inactive users without browse project permission set as watcher when automtically closing an issue by the JIRA Automation Plugin

I am facing this problem for quite a while now:

If an employee leaves the company his account gets deactivated. In some tickets he is still set as watcher.

We close most issues by using the JIRA automation plugin's 'transition issue action'.
If one or more inactive users are set as watcher, the action will end in an error saying:

"Users do not have permission to browse issue: username"
So every time that error occurs I have to manually remove the affected watches.


Is there a way to ignore / skip this check or is it just a bug?

Just as an additional note: we have Watcher Custom Field for JIRA installed.


Does anyone else face this issue as well?
Any ideas are appreciated.



This seems to happen because of the Watcher Custom FIeld for JIRA.
I created an issue for the developer:

Inactive users are currently not ignored when check Browse Issue permission while transitioning the issue.
The developer will fix this with the next release.

1 answer

1 accepted

1 vote
Answer accepted


I'm not familiar with Watcher Custom Field for JIRA but it looks like there is an issue with the way this plugin interacts with the transition of an issue. Automation plugin only tells JIRA to perform the transition as the 'actor' user (which I assume still exists and is active).

You may try something like and bulk-update the custom watchers field.

Hi Matej,

thank you for your information. I will have a look.
Moreover, I created an issue in Bitbucket for the Watcher Field Plugin:

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

568 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you