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

As a Rapid Board user, I would like the remaining effort of a story being based on quick filter results

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

      We use the quick filters to show only certain aspects (subtask types) of a story. At the moment the remaining effort is always based on all subtasks and does not consider the quick filter results.

      We want the remaining effort of a story being based on the results of the quick filters.

      The swim lanes already show the task count based on the quick filters (01-QuckFilterBasedRemainingTaskCount.png). Why not add the remaining effort there (02-WhatWeNeed.png)?

        1. 01-QuckFilterBasedRemainingTaskCount.png
          28 kB
          Bernd
        2. 02-WhatWeNeed.png
          26 kB
          Bernd

            [JSWSERVER-9178] As a Rapid Board user, I would like the remaining effort of a story being based on quick filter results

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068793 ] New: JAC Suggestion Workflow 3 [ 3663639 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Atlassian Update – 7 August 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 now.

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

            We hope you will appreciate our candid and transparent communication. 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 – 7 August 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 now. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers) within the last year. We hope you will appreciate our candid and transparent communication. 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
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625591 ] New: JAC Suggestion Workflow [ 3068793 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327187 ] New: Confluence Workflow - Public Facing v4 [ 2625591 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044011 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327187 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032171 ] New: JIRA PM Feature Request Workflow v2 [ 2044011 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736315 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032171 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: triaged New: affects-server triaged
            Martin (Inactive) made changes -
            Business Value Original: Enhanced [ 10502 ]
            Workflow Original: GreenHopper Kanban Workflow v2 [ 536086 ] New: JIRA PM Feature Request Workflow v2 [ 736315 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]

              Unassigned Unassigned
              92781a263664 Bernd
              Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: