-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
7.1.0, 7.2.10, 7.3.8
-
7.01
-
7
-
Severity 2 - Major
-
32
-
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Issue Summary
When a user creates a sub-task, it is expected to inherit the parent issues components however since JIRA 7.1.X this stopped being so.
Steps to replicate
- Craete a test project.
- Create components for this project.
- Add the component field to the view/edit screen.
- Create an issue in the test project.
- Assign components to this issue.
- Create a sub task for the issue using More > Create Sub-Task
Expected Result
JIRA would create the sub-task and it would inherit the components of it's parent issue.
Actual Result
JIRA creates the sub-task but clears out the component field.
Notes
- Same problem for Versions from parent issue.
- This is undocumented feature (see
JSWSERVER-11784) and specific to Software (Agile) projects.
Workaround
None
- causes
-
JRASERVER-14810 Sub-tasks quick creation for should inherit the components of the parent issue for new sub-tasks
- Gathering Interest
- is duplicated by
-
JRASERVER-46073 Fix Version is not Copied to Subtask when Creating Subtask
- Closed
-
JSWSERVER-15797 Sub-Task No Longer Inherits Parent's Component Field
- Closed
- is related to
-
JRASERVER-5225 Sub-tasks should inherit selectable fields from the parent task
- Closed
-
JSWSERVER-11784 We should update our documentation regarding versions and sub-tasks
- Closed
- relates to
-
JRASERVER-6398 Subtask should inherit (some) fields from parent task as default values
- Closed
-
JRACLOUD-60414 Sub Task Stopped inheriting Parent components
- Gathering Impact
-
RAID-618 Loading...
- was cloned as
-
JDEV-36726 Loading...
-
JSEV-81 Loading...