-
Suggestion
-
Resolution: Won't Do
-
1
-
10
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Carol Low
clow@atlassian.com
Product Manager, Jira Cloud
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
We would like to be able to mark an issue open to certain people who would otherwise not have access to it, either through project or issue priority schemes.
What we initially thought we could do was to mark the users as watchers of a particular issue, which would then allow the user to get emails when the issue changes. While this works (apparently due to bug JRA-5743), it doesn't allow the user additional access to the issue over time through the web interface. What we would like is an additional option on the Issue Security Scheme to support allowing anyone marked as a watcher of an issue to be able to be in a security level.
The particular use case is:
- User submits a "help desk" request. This goes to the "Help Desk" project
- The Help Desk project has a "Reporters and Developers" issue security system
- Developer realizes that this requires development (rather than just a quick fix) and is already being tracked by an issue in the "Core" project
- Developer marks the "Help Desk" issue as a duplicate of the "Core" issue and makes the original reporter of the "Help Desk" issue a watcher on the "Core" issue
- From here, while the reporter would otherwise not be able to see anything in the "Core" project, because a developer has made him watch that issue, he should be able to see it.
This was originally tracked in the Atlassian support system as JSP-864.
- duplicates
-
JRACLOUD-5621 Add all watchers to a Security Level
- Closed
- is duplicated by
-
JRACLOUD-43464 Allow Watchers to be added to Issue Security Level
- Closed
- is related to
-
JRASERVER-5982 Watcher Issue Security Field
- Gathering Interest
- relates to
-
JRACLOUD-5621 Add all watchers to a Security Level
- Closed
-
JRACLOUD-45488 Add Watchers to Issue Security Level
- Closed