Status: Resolved (View Workflow)
Resolution: Won't Fix
Affects Version/s: 3.4.1, 5.2.6
Fix Version/s: None
Component/s: Project Administration - Permissions
Environment:Effects all sub-task cabable Versions: JIRA Enterprise and Pro Versions since Verion 3.0
It became a best practice to define a feature request, improvements etc. as a parent issue and
to break down the implementation tech details into sub-tasks.
Unfortunately, everybody with permission Create Issues is able to create sub-tasks.
There is no way for project lead to enforce a
- "How to create a sub-task" policy
My improvement request: please add a new permission type
- Create Sub-Tasks
Based on this improvement, a project lead will be able decide whom to give the permission
to create sub-tasks (e.g. to experienced team members), and not give (e.g. customers, etc.)
BTW, please consider to rename sub-task to sub-issues to become more consistent - check JRA-6923.