Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-5225

Sub-tasks should inherit selectable fields from the parent task

    XMLWordPrintable

Details

    • 37
    • 63
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      23rd December 2015

      Hi all,

      Thanks for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.

      We have revisited this issue again recently and wanted to reiterate that there are still currently no plans to implement this suggestion, and it is not currently on any JIRA team’s roadmap at this stage.

      In the meantime, you might be interested in checking out the following solutions available on our Marketplace:

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Kerrod Williams
      Kerrod (dot) Williams (at) atlassian (dot) com
      Product Manager, JIRA

      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.

      Workaround

      Create an automation rule to sync parent and child issues. Example: Auto close parent issue when all sub-tasks are done (sync). Please keep in mind your Automation service limits

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller
              Votes:
              621 Vote for this issue
              Watchers:
              356 Start watching this issue

              Dates

                Created:
                Updated: