This issue is 17 years olad and many of us would still find it useful. It' seems like a really basic use case to me. Our security level allows administrators, developers, reporter and assigneee access. Often the reporter has viewer only role which means they can't see other secured tickets. However sometimes we would want their boss, or someone else within their department to be abvle to follow the ticket as well. Currently we are unable to do that without adding yet another custom (,multi user selection) withint the project and adding the various people to that. That is ridicuously complex when the entire point of having the existing watchers field is to allow all watchers of that ticket to see and follow it!

This ticket has been around since before 2005, it still seems a crucial bit of functionality to anyone using Issue Security. Are there any plans to give us an option to include watchers in the issue security?

That's troubling since the Watcher plugin have become pretty critical to many businesses. It's also been the recommended method for adding watchers on Issue Creation by Atlassian. I have an old fork of the code here...perhaps someone has a more recent copy to continue on the work.

7bc97e81aad0 They haven't discontinued Data Centers, only Servers. For now at least...

Now that Jira Watcher Field by Ray Barham has evaporated from both Atlassian Marketplace and Bitbucket, this ticket becomes even more noteworthy.

Atlassian has officially abandoned their on prem product so you can forget about any updates.

Thanks to Atlassian's poor management we've given up on their products entirely and have moved to Gitlab + other tools.

I can't believe that this ticket is 16 years old!

This is incredibly frustrating to not be able to do that. This causes a huge problem where we basically cannot use security properly.

Unfortunately, with an issue this old, I have no hope that this will ever be fixed...

I just implemented this in our Jira 4.3.4. There was an interesting aspect of this tho: if you want to add someone to an issue as watcher, he/she needs to able to see the issue (browse permission and issue security). But you cant add him/her, since he/she cant see the issue. So I modified the watcher manager class, when you try to add someone as watcher to an issue which has issue security and this security has this rule (watchers can see the issue) then I dont check if the user can see the issue.

I have the same request, also in a help desk environment. We have also set the security level on "reporter" so users can only see their own issues. However, we would also like other users from the same company for instance, to be able to view and edit the issue. Setting security level on watchers would probably solve this issue for us, since we could add the group which represents all users from that company to the watch list.

Technically this should be possible - as we would just need a different permission type (much like reporter & assignee). However, we would need to throw new events when a watcher is added or removed, as we would need to reindex the issue.

There are probably two things that we should do before we attach this bug:

• Throw more events throughout JIRA, and use a pluggable event architecture system
• Allow different parts of the system to automatically listen for events. This could be through Pico.