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

Track story point velocity per resource based on releases

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • Plans - Timeline
    • None

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

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      As a Kanban/scrumban team, I would like velocity estimations to be determined by how many story points that a given resource had completed within a release period, so that I can make accurate projects in JPO.

      In my project, that looks like this....
      Each resource that has the skill of development will be automatically appended to the "developer" field when they take on the work. We release "fixVersion" field every two weeks. The estimates section in the "backlog" tab determine how many story points each skill is mapped to. So on release there is a number of story points that each "developer" "UAT" "tester" has accomplished. That is the number that I would want my projections to be based on.

        1. CSE - Scrum Portfolio (1).xml
          653 kB

            [JRACLOUD-89764] Track story point velocity per resource based on releases

            Deleted Account (Inactive) added a comment -

            Please remove this attachment. I would like to send the hidden data version instead. Thank you.

            Deleted Account (Inactive) added a comment - Please remove this attachment. I would like to send the hidden data version instead. Thank you.

              Unassigned Unassigned
              3a493c5b-f377-4197-86bd-02c225f7ea96 Deleted Account (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: