Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can I set a *global* watch on a certain project and set email watches for *all* users in Fisheye/Crucible?

As an administrator, I want to set a watch for a certain repo/branch/whatever for all users and at the same time set email watches to immediate for all users as well. I want all users to be notified of any changes.

Is it possible?

5 answers

1 vote

FishEye watches are meant to be managed by individual users, administrator can allow/disallow watches for particular repositories or globally for all repositories, but individual users are expected to enable those watches then.  See

There is a plugin provided though to allow administrators to control actual watches for individual users or group of users, see  Perhaps you want to give it a try?

I'd like to see something where the admin can add watches for an email address instead of a user. We have some group email addresses that I want to notify of SVN changes, and not all of them are Fisheye users.

Anybody? help please


When I "Allow users to watch for repository changes", the user will not have anything in his watch list. Why is that? shouldn't it be automatically added to his list? the user won't be receiving any email watch if his list is empty, isn't that right?

According to the documentation, folks can configure their own Watches, or you can configure watches for them for a single repository or all repositories.  If you want it down at the branch level, you'd probably have to define that specific branch as its own separate repository in Fisheye (shouldn't negatively affect parent/main repo). 

See Watches documentation

As an admin, my experience is that folks have a tendency to ignore email notifications from Fisheye/Crucible if they get too many, and I actually recommend they configure their Profiles for specific batch notifications of only some notifications for that reason.  You might end up with an "automatic delete" behavior if you make this mandatory instead of voluntary. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

297 views 0 9
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you