-
Bug
-
Resolution: Won't Fix
-
Medium (View bug fix roadmap)
-
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
-
JSWSERVER-15797 Sub-Task No Longer Inherits Parent's Component Field
-
- Closed
-
-
JRASERVER-46073 Fix Version is not Copied to Subtask when Creating Subtask
-
- Gathering Impact
-
- 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...
[JSWSERVER-16018] Sub Task in Software project doesn't inherit Parent components
Remote Link | Original: This issue links to "Page (Extranet)" [ 317105 ] |
Link | New: This issue causes JRASERVER-14810 [ JRASERVER-14810 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 470927 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 469995 ] |
Minimum Version | New: 7.01 |
Workflow | Original: JAC Bug Workflow v2 [ 2856107 ] | New: JAC Bug Workflow v3 [ 2938118 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546050 ] | New: JAC Bug Workflow v2 [ 2856107 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1544163 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546050 ] |
Current Status |
New:
Hi Folks,
This is not a feature , It was a FUG. It was a side affect of Classic Boards. Once Classic Boards where removed the feature got removed along with them. It existed up to 7.0.X and it was gone starting from 7.1.0. It only worked on JIRA Software instances. With JIRA Software installed the fug was available for all projects including Business (JIRA Core) ones. We won't be fixing it as it's not a bug. However, we are considering adding a fully fledged solution in the up-coming releases. I'm going to close this one as "Won't fix" and add a new ticket with issue type "Suggestion" where we are going to keep you up to date about adding this new feature. Please watch and comment: https://jira.atlassian.com/browse/JRASERVER-5225 Sorry for all the fuzz. Pawel Farid JIRA Server Dev Manager. |