Anusha Rutnam added a comment - 16/Jan/2024 7:26 AM Atlassian Update - January 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

Stefan Pinter added a comment - 02/Sep/2020 1:53 PM - edited this is very relevant for us, because this way (customers can be watchers and thus receive notifications that are not meant to be sent to customers) it already happened, that customers receive information that was intended to be internal only. i wonder what the best practice is. relying on users not to add customers to the watchers list? as administrators we want to restrict this, so that sensitive data does not leak somehow.

Rudi Pillich added a comment - 21/Oct/2014 9:48 PM Maybe for simplicity, ASSIGNABLE assignees, reporters and watchers could be traeted all together... this means that, if a particular user is denied to be an ASSIGNABLE assignee, he is also automatically excluded from being an ASSIGNABLE reporter and watcher.