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

[Ziad]

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?

[Piotr Swiecicki]

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 https://confluence.atlassian.com/display/FISHEYE/Watches

There is a plugin provided though to allow administrators to control actual watches for individual users or group of users, see https://marketplace.atlassian.com/plugins/com.atlassian.fisheye.plugins.fisheye-watchers-plugin  Perhaps you want to give it a try?

[J]

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.

[Ziad]

Anybody? help please

[Ziad]

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?

[Tini Good]

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.