Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Editing stages that pull in to velocitychart

Amy Glass
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2020

When looking at the velocity chart for my team, it pulls in 'estimated' and 'completed.' I'd like to edit the stages that pull into the 'completed' category. I'd like it to also pull in 'ready for acceptance' that we have setup, which is after code review. Sometimes the work is done but is not released yet and we want those stories and points to show as completed because the work is done. I'm not seeing a way to do that. Does anyone know if you can and where?

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 18, 2020

Hi @Amy Glass -- Welcome to the Atlassian community!

The velocity chart shows the completed work at the end of the sprint.  "Complete" is determined for the statuses in the rightmost column for your JIRA scrum board.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/

From what you describe, your team is using scrum. But, I cannot quite visualize your workflow.  Maybe you could post an image of your board settings with the columns and status mapping.

 

You seem to be saying that work is "dev complete" and not released, but you want to count it as done for purposes of velocity reporting.  You have a few options to do what you want, although some of them are not aligned with agile practices and so could cause issues:

  • Move the items to done, and remove any release steps from the board, ignoring that remaining work
    • This will reduce visibility of the in progress work and probably increase work in progress (WIP)
  • Separate your delivery and release workflows onto two boards
    • This could lead to task switching between delivery and release work, increase WIP, and confuse people on the priorities
  • Add the release steps to the board, and investigate ways to use smaller chunks/releases to fit delivery within a sprint time-frame
    • This will force the team to slow down, and fully finish the work that is in progress
    • It will also encourage the team to consider how to improve workflow and release methods
    • It will give you a better idea of how much your team can fully complete during a sprint

Best regards,

Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events