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

As a user I want to be able to see the Remaining Estimate on Rapid Board cards instead of the Original Time Estimate

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

      You would normally only look at a sprint board once the sprint has started, and when a sprint has started the only valu ethat is relevant for any given sprint task is the remaining estimate. Therefore this should be visible directly on the rapid board cards in stead of the Original Time Estimate.

      This will give a far better overview of the sprint, when viewing the entire Rapid Board.

      As a bonus it would be very nice if the value is editable directly on the Rapid Board cards.

      COS:

      • On work mode the lozenge will show remaining estimate
      • For parent stores this will not include sub tasks
      • Only if time tracking is enabled

            [JSWSERVER-5616] As a user I want to be able to see the Remaining Estimate on Rapid Board cards instead of the Original Time Estimate

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3065659 ] New: JAC Suggestion Workflow 3 [ 3656198 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2623741 ] New: JAC Suggestion Workflow [ 3065659 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2324820 ] New: Confluence Workflow - Public Facing v4 [ 2623741 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2042296 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2324820 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030342 ] New: JIRA PM Feature Request Workflow v2 [ 2042296 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 737443 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030342 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Business Value Original: Expected [ 10501 ]
            Workflow Original: GreenHopper Kanban Workflow v2 [ 400359 ] New: JIRA PM Feature Request Workflow v2 [ 737443 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Thanks Shaun. A good read.

            Anders Holm added a comment - Thanks Shaun. A good read.

            Hi anders holm,

            Using remaining estimate for the sprint commitment will corrupt velocity, so only the original estimate is shown on the cards. More discussion on this is in this answers post.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi anders holm , Using remaining estimate for the sprint commitment will corrupt velocity, so only the original estimate is shown on the cards. More discussion on this is in this answers post . Thanks, Shaun

              Unassigned Unassigned
              e8d39c321546 Anders Holm
              Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: