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

Ability to see 'Issues Missing Estimate' in 'Workload by Assignee' summary

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • 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.

      As originally discussed on the related issue JSW-11177.

      Per row metrics (assignee) similar to

      • Issues
      • Issues Missing Estimate
      • Original Time Estimate
      • Remaining Time Estimate
      • Time Spent (tracked at JSW-14771)

      "Missing Estimate" is only a count of issues that are missing estimates.
      "Remaining Estimate" is not an accurate reflection of remaining work or when exactly we should expect to be completed if everything goes according to the plan (estimate), if there are incomplete issues with remaining estimate = 0

      • So any ticket that has not been estimated would fall into that category,
      • Plus any ticket that is not in Resolved or Done state, and although it might have had an estimate at some point, but the current remaining estimate = 0

      Having an idea of how many such tickets are in the sprint (current or the one being planned) gives us a better assessment of the situation.

          Form Name

            [JSWSERVER-14827] Ability to see 'Issues Missing Estimate' in 'Workload by Assignee' summary

            Gosia Kowalska added a comment -
            Atlassian Update – 29 September 2019

            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.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 29 September 2019 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. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

              Unassigned Unassigned
              mjopson Martin (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: