Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-5225

Sub-tasks should inherit selectable fields from the parent task

    XMLWordPrintable

    Details

    • 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:

      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

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              cmiller@atlassian.com Charles Miller
              Votes:
              634 Vote for this issue
              Watchers:
              383 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: