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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Extract data from a burndown chart

Hello,

Is there a possibility to extract data from a burndown chart? I've been trying to create a filter with all the "scope change" tickets but haven't had success.

Regards,

SY

2 answers

0 votes
Brant Schroeder Community Leader Mar 10, 2021

@syee - Welcome to the community.  Unfortunately there is no way at this time to export data from burndown charts.  If you have ScriptRunner I believe you can use the following to get the information you are after.

issuefunction in addedAfterSprintStart(board-name, [sprint-name])

issuefunction in removedAfterSprintStart(board-name, [sprint-name])

@Brant Schroeder thank you very much!

Hi @syee  -- Welcome to the Atlassian Community!

You have two questions, with some overlap between them.

 

1) Is there a possibility to extract data from a burndown chart?

No, but you can pull the Sprint Report as JSON for a completed sprint using the REST API, substituting in yourCompanyInstanceURL, yourBoardNumber, and yourSprintNumber

yourCompanyInstanceURL/rest/greenhopper/1.0/rapid/charts/sprintreport?rapidViewId=yourBoardNumber&sprintId=yourSprintNumber

 

2) I've been trying to create a filter with all the "scope change" tickets but haven't had success.

This is not possible with out-of-the-box Jira JQL. If you have one of the marketplace scripting  or reporting addons, several have features to support this.  For example, ScriptRunner.

Without a marketplace add-on, there are a few work-arounds:

  • You could export issues to a spreadsheet, and use formulas on the Sprint column to determine scope change.  This will probably be incomplete information.
  • You could use the REST API and expand the changelog for issues to automate what could be done manually looking at each issue
  • You could use custom fields and automation rules to automatically detect this for future sprints, but not previously closed sprints

 

Best regards,

Bill

Hi @Bill Sheboy !

Thank you for your help.

Regards,

SY

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

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