-
Suggestion
-
Resolution: Unresolved
-
3
-
10
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thank you for taking the time to share your challenges around sub-task permissions. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the next 12-18 months. We will be maintaining this ticket's status as "Gathering Interest" in order to continue learning from all of you about pain points and challenges relating to this suggestion, and will continue to re-visit this ticket in our ongoing product planning.
We recognise that the lack of granular issue permissions can be a major challenge in using Jira, which is why we are taking steps to improve the flexibility of our permission scheme at all levels. That journey begins with our Extended Project Admin capabilities, which will be released by the end of this year, and which we hope will be just the first step in making Jira permissions more granular and powerful.
We understand that this is not the update you may have been hoping for, especially given the longstanding nature of this issue. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Aditi Dalal
adalal@atlassian.com
Product Manager, Jira Cloud
It would be very useful for us to have two new permission added to JIRA's set of permissions
- edit sub-task
- delete sub-task
(We want to be able to assign those permissions to Reporter.)
- is related to
-
JRACLOUD-8521 Add permission type Create Sub-Tasks ( better: Create Sub-Issues )
- Closed
-
JRASERVER-10075 Add "Edit sub-task" and "Delete sub-task" permissions
- Gathering Interest
- relates to
-
JRACLOUD-5869 Sub-Task should have independent security levels
- Closed
1.
|
Test Sub task for dev | Closed | Unassigned |