597
Customers have installed this app in at least 597 active instances.
by Arteziofor Jira Server 8.0.0 - 8.6.1 and more versions
Versions available for Jira Server 5.0 - 7.13.12
Unsupported
This app isn't formally supported.
Supported
Artezio supports this app.
Unsupported
This app isn't formally supported.
Create burndown/burnup charts in Jira with a simple yet powerful gadget
Create burndown/burnup charts in Jira with a simple yet powerful gadget
Create burndown/burnup charts in Jira with a simple yet powerful gadget
Artezio Burndown Chart Gadget
Gadget Options
Data panel
Artezio Burndown Chart Gadget
Customize burndown options. Create burndown charts for week, month or any other period of time
Display all data, used in the burndown chart, as a table in data panel
More details
About Artezio Burndown Chart
Artezio Burndown Chart is a simple yet powerful Jira gadget for creating burndown charts - graphics representing the work left to do versus time. It is a run chart of outstanding work, which is useful to predict when all the work will be done. Burndown charts often used in agile software development methodologies such as Scrum and can be applied to any project containing measurable progress over time.
Reviews for cloud
(6)Sign in to write a review
Nice but very basic. Main problem: burndown does not correlate to releases or sprints.
Solution would be:
=> allow linking it to sprint completion or -more important for us- release (version) date
-> Period Time: derived from release date
-> issues to be implemented (burned down) derived from issues linked to sprint / release
This is a really nice burndown chart. It is easy to configure and looks nice. We use it as an hourly burndown chart to complement the story point burndown chart provided by Atlassian. I highly recommend it if you are looking for a similar solution.
The only negative point that I have come across is that the gadget takes up a lot of room. Underneath the burndown chart (but within the gadget), there is a lot of whitespace. You can view an example here: http://1drv.ms/1EA8d5F
Really good burndown I think. Only things I miss is to be able to set the time of day wf where the period starts and ends. And I am not sure what "Show Closed Issues does" I am guessing it shows the number issues of status "closed" but we don't use that, we use resolved only (for subtasks) so it does not work for me, maybe if we could specify what "closed" means?
Excellent gadget! It will not frighten you with complexity - there is no cumbersome things. Just use it with pleasure!
This is a very simple yet powerful gadget. Just add it to a dashboard, enter a project or a filter name and you ready to build a burn down chart. I like that it is very careful with large amounts of data and you can always stop chart building if your filter is not correct. There are some other cool options like for example now-working days.
Reviews for server
(6)Sign in to write a reviewNice but very basic. Main problem: burndown does not correlate to releases or sprints.
Solution would be:
=> allow linking it to sprint completion or -more important for us- release (version) date
-> Period Time: derived from release date
-> issues to be implemented (burned down) derived from issues linked to sprint / release
This is a really nice burndown chart. It is easy to configure and looks nice. We use it as an hourly burndown chart to complement the story point burndown chart provided by Atlassian. I highly recommend it if you are looking for a similar solution.
The only negative point that I have come across is that the gadget takes up a lot of room. Underneath the burndown chart (but within the gadget), there is a lot of whitespace. You can view an example here: http://1drv.ms/1EA8d5F
Really good burndown I think. Only things I miss is to be able to set the time of day wf where the period starts and ends. And I am not sure what "Show Closed Issues does" I am guessing it shows the number issues of status "closed" but we don't use that, we use resolved only (for subtasks) so it does not work for me, maybe if we could specify what "closed" means?
Excellent gadget! It will not frighten you with complexity - there is no cumbersome things. Just use it with pleasure!
This is a very simple yet powerful gadget. Just add it to a dashboard, enter a project or a filter name and you ready to build a burn down chart. I like that it is very careful with large amounts of data and you can always stop chart building if your filter is not correct. There are some other cool options like for example now-working days.
Reviews for Data Center
(6)Sign in to write a reviewNice but very basic. Main problem: burndown does not correlate to releases or sprints.
Solution would be:
=> allow linking it to sprint completion or -more important for us- release (version) date
-> Period Time: derived from release date
-> issues to be implemented (burned down) derived from issues linked to sprint / release
This is a really nice burndown chart. It is easy to configure and looks nice. We use it as an hourly burndown chart to complement the story point burndown chart provided by Atlassian. I highly recommend it if you are looking for a similar solution.
The only negative point that I have come across is that the gadget takes up a lot of room. Underneath the burndown chart (but within the gadget), there is a lot of whitespace. You can view an example here: http://1drv.ms/1EA8d5F
Really good burndown I think. Only things I miss is to be able to set the time of day wf where the period starts and ends. And I am not sure what "Show Closed Issues does" I am guessing it shows the number issues of status "closed" but we don't use that, we use resolved only (for subtasks) so it does not work for me, maybe if we could specify what "closed" means?
Excellent gadget! It will not frighten you with complexity - there is no cumbersome things. Just use it with pleasure!
This is a very simple yet powerful gadget. Just add it to a dashboard, enter a project or a filter name and you ready to build a burn down chart. I like that it is very careful with large amounts of data and you can always stop chart building if your filter is not correct. There are some other cool options like for example now-working days.
Cloud Pricing
Server Pricing
Data Center Pricing
Artezio provides support for this app.
Vendor support resources
Documentation
Find out how this app works.
See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.6.0 • Jira Server 8.0.0 - 8.6.1 • Released 2019-04-25
Summary
Jira 8 compatibility
Details
Jira 8 compatibility
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Artezio Burndown Chart for Jira via search. Results include app versions compatible with your Jira instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older Artezio Burndown Chart for Jira versions compatible with your instance, you can look through our version history page.
Similar apps
My.com Calendar
Xray Test Management for Jira
Rich Filters for Jira Dashboards
TM4J - Test Management for Jira
eazyBI Reports and Charts for Jira
Jira Misc Custom Fields (JMCF)
Insight - Asset Management
Worklogs - Time Reports for Jira
WorklogPRO - Timesheets for Jira
Tempo Budgets
Enhancer Plugin for Jira
Time to SLA
OKR Board for Jira
Agile Dashboard for Project Management
Work Time Calendar for Jira
QMetry Test Management for Jira
Polls for Confluence
sumUp for Jira
Timesheet Reports and Gadgets
Zephyr for Jira - Test Management
Assets and Inventory Plugin for Jira