Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Version & Epic Report Burn-up/down vs Different Fields

Problem: Some product delivery teams can only have quarterly releases.  Stories collect in a 'Ready for Release' column before 'Done'/'Complete,' but this makes the Version & Epic Report Burn-up/down ineffective as they are not 'complete.'  Can the Version & Epic Report Burn-up/down reports be driven off of another column (such as 'Ready for Release')?  What is the best path to be able to leverage the reports in Jira in this scenario?  

1 answer

Hello @Mark Dewald 

Welcome to the community.

In your Version report do you want to consider the Version 'complete' if the changes have not been Released?

For the Epic Burn-up/down reports also, should the Epic be considered 'complete' if the changes have not been Released?

If the Version and the Epics are not 'complete' until the changes are released, then the reports are accurate.

If you want to the reports to indicate the work is 'complete' when the issues are in the "Ready for Release" status, then that status needs to be part of the Done Status Category and it needs to be mapped to the right-most column of your board. Do you use sprints? If you do, then the issues would also be considered "done" for the sprint when they are in the "Ready for Release" status.

The reports are based on the Status(es) mapped to the right-most column of your board. You cannot make them report based on a different column.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

199 views 0 7
Read article

Community Events

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

Events near you