The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to restrict external users from adding in to Watchers

Vallala Ujwala
April 7, 2025

We are trying to restrict external users from adding in to Watchers but need to be added in Request Participants 

We have used listener to restrict users however the count is not updating .Is there any way to update count (on refresh count is disappearing)

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Robin Kon
Contributor
April 7, 2025

Seen this happen when you try to control Watchers via a listener, especially if you're modifying it post-issue-update. The count not updating usually means the UI isn't getting the new state in real-time, or the listener logic isn't fully blocking the change at the right event timing.

We had a similar setup where we allowed external users as Request Participants but restricted Watchers to internal roles. What worked better for us was using a custom condition inside a workflow validator or a ScriptRunner behavior to prevent the Watcher update entirely before it gets saved, instead of cleaning it up after the fact. Listeners often run too late to update the visible count reliably.

Also, worth checking if your listener is running asynchronously, which would delay the count update until after the page loads. If that’s the case, switching to a sync listener might help with the UI sync issue.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events