Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Differentiate Burnup Report between Deployed and In-Testing

Dear Atlassian Fellow, 


I'm working as a PM in an E-Commerce company and actively use Jira Board to maintain the development of the software. At this phase, the engineer is re-develop to enhance the functionality against the older version of the apps. 

As currently, the software that is being developed started from the white-blank page, after close to the release date to the first MVP, the QA team is stepping in to perform the testing of the apps. 

My question is, how to get the burnup report traceability for both engineer and QA Engineer because each of Engineer and QA should have their own Burnup Report Metric, to ensure what is the deployment rate for engineer and metric for QA testing speed as well as the traceability for both engineer and QA to align between Developing and testing.

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 17, 2022

Burn reports are based on the sprints that you do, which are tracked in boards. 

A board is designed to be a representation of a team's work, and while the usual idea is that a team is cross-functional (so that Development and Testing are done by the team, so they deliver a working item in one go), it's not hard to set up boards that support having two teams work separately on the same issue.

The way to do this in your case is to define a workflow that has a clear set of development steps, and another set of steps for QA, so that each team is looking at the issues on their boards and hence able to generate burn reports appropriate for their team.

The most obvious and simple example of this is to define 


  • To do -> in dev -> dev done / ready to test -> in test -> closed

Developer board columns:

  • To do: To do
  • In progress: in dev
  • Done: dev done / ready to test, in test and closed

QA board columns:

  • To do: dev done / ready to test
  • In progress: in test
  • Done: closed


Log in or Sign up to comment