Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Do
Fix Version/s: None
Component/s: Issue - Sub-Tasks
Labels:

Support reference count:
18
Current Status:
Hide

20th December 2017

Hi all,

Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer.

We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to make it possible for sub-tasks to inherit selectable fields from the parent task. Therefore we decided to close this issue.

While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level.

Also there are commercial third party plugins available, that provide the requested functionality:

"Quick Subtasks for JIRA" available for Server deployments

"Copy to Subtask Plugin" available for Server deployments

"Field Synch" available for Server deployments

"Issue Templates for JIRA" available for Server deployments

Since investing in the functionality for sub-tasks inheriting selectable fields from the parent task in Jira Server is not aligned with our strategy and roadmap, we will be closing this issue.

Meanwhile, we've decided to prioritise other highly voted suggestions for the near future:

Improved Rich Text Editor

Reduction of challenges related to Mail Server

Handling Jira email chattiness

Allowing users to edit shared filters and dashboards

I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our approach to highly voted Server suggestions here.

Please don't hesitate to contact me if you have any questions.

Regards,
Gosia Kowalska
Senior Product Manager, Jira Server
Show
20th December 2017 Hi all, Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and we are sorry to have kept you so long without a clear answer. We (the Jira Server team) have recently reviewed this suggestion and how it would fit alongside our strategy and other customer priorities. I am afraid we are not planning to make it possible for sub-tasks to inherit selectable fields from the parent task. Therefore we decided to close this issue. While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity on both conceptual and technical level. Also there are commercial third party plugins available, that provide the requested functionality: "Quick Subtasks for JIRA" available for Server deployments "Copy to Subtask Plugin" available for Server deployments "Field Synch" available for Server deployments "Issue Templates for JIRA" available for Server deployments Since investing in the functionality for sub-tasks inheriting selectable fields from the parent task in Jira Server is not aligned with our strategy and roadmap, we will be closing this issue. Meanwhile, we've decided to prioritise other highly voted suggestions for the near future: Improved Rich Text Editor Reduction of challenges related to Mail Server Handling Jira email chattiness Allowing users to edit shared filters and dashboards I understand that our decision may be disappointing, but we also hope that you will appreciate our candid and transparent approach. You can learn more about our approach to highly voted Server suggestions here . Please don't hesitate to contact me if you have any questions. Regards, Gosia Kowalska Senior Product Manager, Jira Server
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

Original request description:

As JIRA user who creates issues and subtasks I want this process to be as easy as possible. Therefore I want the subtasks to assume the values of fields from the parent issue, so that I do not have to enter these values manually. But at the same time I want to be provided with a choice of the fields which will be used for propagation, because clearing redundant fields is going to also cost me some time. Among the propagated fields the following should be allowed for selection as a minimum: affected version, fix version, components and optionally: severity and labels.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

InheritSubTaskFieldsFromParentIssueEventListener.java
4 kB
19/May/2009 5:23 PM
InheritSubTaskFieldsFromParentIssueEventListener2.java
5 kB
12/Nov/2009 5:36 PM
InheritSubTaskFieldsFromParentIssueEventListener.class
6 kB
10/Mar/2011 6:56 PM

Issue Links

incorporates

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-5432 Sub tasks should inherit Version & Component details from parent

Closed

JRASERVER-6398 Subtask should inherit (some) fields from parent task as default values

Closed

JRASERVER-6492 Subtasks do not inherit version information from parent task

Closed

JRASERVER-12118 Set Component/Fix Version in post function does not set a component or version

Closed

JRASERVER-5436 Sub-tasks should inherit parent task values

Closed

JRASERVER-6334 sub tasks should optionally inherit property settings of parent task

Closed

JRASERVER-9440 Ability for sub-task items to inherit properties of its parent item

Closed

JRASERVER-16173 Subtask inheritance

Closed

JRASERVER-17852 Sub Task Should Inherit Parent's Component

Closed

JRASERVER-28740 Copy to Subtask

Closed

JRASERVER-33803 Display parent task fields on subtask views

Closed

JRASERVER-44295 Subtasks should inherit parent task priority

Closed

is related to

JRASERVER-3374 Per issue TODO check list

Closed

JRASERVER-6262 Would be cool if a sub-task would be automatically assigned to the owner of the main task

Closed

relates to

JSWSERVER-16018 Sub Task in Software project doesn't inherit Parent components

Closed

JRASERVER-38672 Document what subtasks inherit from their parent

Closed

JRASERVER-42273 As a user, I'd like to be able to view certain fields from the parent issue in the sub-task

Closed

JRACLOUD-5225 Sub-tasks should inherit selectable fields from the parent task

Gathering Interest

links to

The enviroment is JIRA ondemand (Cloud). Is it possible some how arrange that certain issue type contains/opens always some Predefined Sub-Tasks automatically?

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Wiki Page Loading...

(8 is duplicated by, 2 is related to, 4 relates to, 1 links to, 17 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Charles Miller

Votes:: 634 Vote for this issue

Watchers:: 383 Start watching this issue

Dates

Created:: 15/Nov/2004 2:54 AM

Updated:: 11/Apr/2023 8:23 PM

Resolved:: 20/Dec/2017 9:06 AM