I am keeping track of bug fixing for multiple projects, and would like to create graphs that show the total amount of created vs. the resolved issues on a weekly basis.
By total, I mean not just the amount of created vs resolved bugs during that week (like in the "created vs resolved graph"), but over the lifetime of the project. So for example, if the project had 100 created and 50 resolved bugs before the shown period in the graph, the graph should start with 100 created and 50 resolved bugs and show the progression from there throughout the shown period.
This way we could see how many bugs are in our database and how many of those are yet to be fixed, so we can easily see how much focus we should put on bug fixing.
Alternatively, I suppose I could use a graph that shows the amount of Open or Unresolved issues per day, although this wouldn't show the quantity of bugs being processed.
Is either of this possible?
Hi @Rik Koning ,
In the 10 gadgets offered by the add-on, there is a Release Burndown / Burnup Chart gadget than can be easily configured as Created vs Resolved Chart. Just take a look at this example.
Please feel free to try xCharts - Custom Charts & Reports . It provides a lot of built-in templates to create custom charts.
In addition you can script your own charts & reports, using Groovy.
If you have any questions, please feel free to contact me directly via email to: n.werle(at)decadis.de
the Created vs. Resolved - Chart - Gadget has a setting ("Collection Operation -> Cumulative") that will exactly do what you describe except one thing: the graph is beginning with 0. But you can start displaying data more than four years in the past, so this might be sufficient for you.
I have found that option, but the problem with it is that I want to show on a weekly or biweekly basis how we did during that period, so then I would have to cut the graph off before that period instead of just saving and printing it. Since I need to do this for a large amount of projects, it would not be ideal.
It might be a good alternative, but I'm hoping there is an automated way of achieving this.
Additionally, I have a project that was migrated from another project, so this would show a very strange graph with 200 issues created on the first day that will heavily distort the graph. Again, not a big deal, but I'm hoping to prevent this.
mm, I see.
Maybe you could split your data and create a dashboard with two gadgets (at least):
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
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