I configure a project with two boards, the first board is for development and the second one is for QA purposes, so the project issues (Stories and Bugs) start in the Dev Board and Ends in the QA board.
So the first board has 4 statuses, "To Do", "In Progress", "Code Review", And "Dev Done", this last is configure as a DONE status in my workflow.
When a card reaches the "Dev Done" status automation rules move the card to the QA Board changing the status to "QA Pending".
The Sprint report for the DEV board shows me all cards that reach the "Dev Done" status, but the burndown chart remains as a flat line.
Any idea of how I can use the print report for the first board?
Hi @Hender Ruiz
The boards and reports seem correct, as your team (dev) is doing part of the work, calling it "done", and then re-opening the work for the other team (QA). So the clock resets.
There are a few approaches to solve this as the teams have decided to split completing work into two stages, both are needed to deliver value to your customers...
Hi! This is a workflow issue, impacted by how your team normally works with defects...
I recommend "taking it to the teams...": Today, what happens to a QA work item when a defect is found? If you currently do one of the above, you probably can use automation to handle it, such as re-open the linked dev issue, or at least notify the assignee that a defect was found.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events