-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
3
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
h5 Problem Definition
When a user on the Security-level add watchers, those users cannot browse/edit the issue because they aren't on the Security-level (which they should never be on unless they need to be part of that specific issue discussion).
To get around this we currently use a custom field ('User Picker') that allows users to be added to field, which is a field set to the Security-level needed to browse/edit the issue.
I have searched Atlassian documentation and plugins, and have not seen a solution for this.
Suggested Solution
Have watchers added to the issue security levels
- is related to
-
- Gathering Interest
- relates to
-
- Closed
[JRASERVER-45488] Add Watchers to Issue Security Level
This is an exact duplicate of the requirement: https://jira.atlassian.com/browse/JRASERVER-5982 which has also never been actioned
The entire point of adding watchers is so that they can follow a specific ticket. Why would you need a separate custom field within the security scheme for that? It's non-sensical. Another follow for this one as well as 5982...
pasting the text of the security levels conf "add" screen.
Add User/Group/Project Role to Issue Security Level
Issue Security Scheme: OGC- Issue Security Scheme
Issue Security Level: OGC-Legal-Review
Please select a user or group to add to this security level.
This will enable the specific users/groups to view issues for projects that:
- are associated with this Issue Security Scheme and
- have their security level set to OGC-Legal-Review
- Application access = Any logged in user
- User custom field value = Choose a custom field
- Project Role = Choose a project role
- Service Desk Customer - Portal Access
- Reporter
- Current assignee
- Single user = Start typing to get a list of possible matches.
- Project lead
- Group = Anyone on the web
- Group custom field value = Choose a custom field
HMMM, I cannot add a screenshot in this ticket. I tried pasting and looked for a way. but I can't, sorry.
Like the others here, I also have a request by one of my departments to be able to add whoever is inserted into the Jira watchers field to be added to the security level.
Asking the users to interact with yet an additional field is going over like a lead ballon.
I cannot see how to solve it without implementing the clunky user picker workaround, which is really like duplicating the watchers field. I guess I might implement some automation that says when the user picker duplicate field changes, make the same change in the watcher field. Seems like a lot of work to rig up something as a workaround. In my opinion it would be cleaner if it were added to the security level config as an option. I.E. in this screen.
Now that Jira Watcher Field by Ray Barham has evaporated from both Atlassian Marketplace and Bitbucket, this issue becomes even more noteworthy.
It seems to be a duplicate of JRASERVER-5982 rather than just related to it.
(https://community.atlassian.com/t5/Jira-questions/Add-watcher-to-issue-security-secured-issue/qaq-p/650715#M403091)
User Picker CustomField is always the suggested solution for this limitation. It's clunky, and diverges from what users are used to using: Watchers.
What you can do is install this add-on: https://marketplace.atlassian.com/plugins/com.burningcode.jira.issue.customfields.impl.jira-watcher-field/server/overview
That'll expose a copy of the watchers as a custom field to use in your Security Schemes.
Is there any plan to realise this issue? i mean the linked issues are from 2005....