- 
    Bug 
- 
    Resolution: Duplicate
- 
    Medium 
- 
    None
- 
    3.1.1
- 
        3.01
- 
        18
- 
        
Subtasks in JIRA 3.1 are very handy, but since they are full-blown JIRA issues, creating them becomes a bigger burden than it should be.
In particular, I think subtasks should inherit, by default, some of the fields from the parent task, in particular
-Priority
-Component
-Affects Version
-Fix For Version
It's ok if they can still be modified but, when creating the subtask, those fields should be initialized to the parent's value.
- duplicates
- 
                    JRASERVER-5225 Sub-tasks should inherit selectable fields from the parent task - Closed
 
- is detailed by
- 
                    JRASERVER-18505 View & Edit Issue Improvements - Gathering Interest
 
- is duplicated by
- 
                    JRASERVER-8818 have subtask inherit component of parents - Closed
 
- 
                    JRASERVER-13669 Would like to have certain feilds prepopulated on subtasks from the parent issue - Closed
 
- 
                    JRASERVER-16219 Changing a Parent Task's Component Does Not Change the Component of the Subtask - Closed
 
- 
                    JRASERVER-22286 Edit sub-task in same operation as the main task(s) - Closed
 
- is related to
- 
                    JSWSERVER-16018 Sub Task in Software project doesn't inherit Parent components -         
- Closed
 
-         
- relates to
- 
                    JRASERVER-3374 Per issue TODO check list - Closed