You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hi everyone,
we transitioned to Jira roughly a year ago and created a bug dashboard some time ago. We are using the Created vs Resolved chart which is really helpful as we can see directly if we can keep up with fixing issues or are lagging behind.
However, what is confusing to me is the fact that the Unresolved trend does not match the total bug count. I already read some of the other posts with questions related to this chart but they were not helpful for me.
What did we do?
- We set the days previously to 420. That makes sure we cover ALL issues ever created
- In total we have currently 191 open issues without a resolution set
- Our workflow properly sets the resolution field for closing & re-opening an issue
What do we expect?
- Actually, I would expect to see 191 unresolved issues for the chart "Trend of unresolved"
Is this assumption correct or are we missing something?
I would suggest you create a JQL Query and try getting the desired results in the query and then continue to display that in the Dashboard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> the Unresolved trend does not match the total bug count. ... I would expect to see 191 unresolved issues for the chart "Trend of unresolved"
Why? A trend is not an absolute predictor, a generaised predictor of direction. It's extrapolated from the data over tiime, it's actaully very rare that a trend would hit your actual count on any given day/week.
Really simple example - lets say we were resolving 1 issue per day for the last few weeks. Your daily numbers would be 1, 2, 3, 4, 5, 6, 7, 8, 9 etc. The trend calculation would therefore predict 10, 11, 12 etc. But let's say I had too much coffee on Wednesday and resolved 3 instead of 1. That would tend to make the trend a bit higher, so it might be predicting slightly higher rates until the spike fades back into the previous trend, but however you look at it, the trend is not predicting exactly what is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting. I was not expecting that Jira really tries to predict a trend.
Then basically Jira does not offer a standard report to show the total amount of bugs? I would need to install some marketplace apps for that or track it on my own, correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The total amount of what bugs?
The daily/weekly numbers opened and resolved are shown in the red/green top chart, which is what that chart is for, so I'm not sure what you're asking for with that. (There's a few things you might mean, I can't be sure which one it might be, need a bit more info before I might be able to identify a gadget or explain the closed/resolved a bit better)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I went for the JQL query to show the current total amount of open bugs. That's fine for now. Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.