Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11225

JIRA Agile should add the original time estimate of the subtasks included in a parent issue

XMLWordPrintable

    • 2
    • 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.

      If subtasks exist in an issue, we estimate only these ones and not the parrent issue.
      When I check the "epic report", the Original Time Estimate is 0 for the issue and this issue is counted for one unestimated issue ! (see attached file)

      It could be really useful to have the addition of estimate values of each sub task in the report, like we can do when the parent issue is showed in the time tracking part (see attached file)

        1. TimeTracking.jpg
          TimeTracking.jpg
          7 kB
        2. Unestimated issue in Epic.jpg
          Unestimated issue in Epic.jpg
          75 kB

            [JSWSERVER-11225] JIRA Agile should add the original time estimate of the subtasks included in a parent issue

            Gosia Kowalska added a comment -
            Atlassian Update – 22 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 22 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              bruno.dorizy Bruno
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: