I'd like to generate a bug summary report automatically in JIRA which can be shown to my boss everyday. Once I use the format in a table:
The record numbers with hyperlink can be clicked in and then others can see detail bug list. I save the search criterial in bugdb and then link it to the record number field.
Is there any way that I can automatically get such report in JIRA? So that I can save my time and do not need to check the record numbers every day and update it manually?
I'm not sure how you determine the difference between Dev Backlog and QA Backlog, but I suppose you might come pretty close already using the two dimensional filter statistics gadget on a dashboard.
First, build a JQL filter to collect the bugs you want to report on. Save the filter and make sure to share it with your boss. Next, on a (new or existing) JIRA Dashboard, add a two dimensional filter statistics gadget. I assume Dev and QA backlogs are separate JIRA Projects (if not, have a look at how you distinguish between them in your instance). So configure the gadget to report on Priority and Project as your two dimensions.
The result should come close to what you designed above.
I was finally able to create my dashboard and add gadget like this:
But is there a better way that can show one graph with several filters? Just like the above table I drawed.
QA Backlog means bugs @ QA side;
Dev backlog means bugs @ Dev side;
For some reason, your screenshot is not showing. So it's kind of difficult to go into more detail about that. Depending on how you have set up your JIRA configuration, I would expect to see multiple lines in your result.
If that's not the case, you could add multiple gadgets on your dashboard presenting you more specific summaries for dedicated filters. Or if you are looking for a powerful, more graphical way of reporting on your data, you could have a look at a reporting add-on such as EazyBI. That comes with a lot of possibilities, but also with a learning curve.
I see the screen shot now. The only thing missing - in my opinion - is how you define QA side and Dev side as a unique piece of information. If you can do that and you replace the 'Assignee' dimension with that piece of information, you will have a report that has the data and click-through functionality you were looking for from the start.
Yes. You're right. Do you know how to define QA side and Dev side?
I know which members are QA, and which members are Dev. - This is from resource aspect.
And also I know which bug status is for QA (i.e, 30, 80) and which bug status is for Dev(i.e, 11, 35, 37) – This is from bug status aspect.
Either one can work for me.
Do you have such experience? Do I need to use easyBI for such use?
To be perfectly honest, using status to determine if a bug is QA or Dev related feels kind of awkward to me. Ok, a bug may be discovered by QA or while an issue was in Dev, but then I would suspect you create a bug issue which moves through a process (to do > in progress > done). As soon as the bug's status changes, you lose the information about where it originated.
So maybe you could start using labels or a custom field to indicate the bug origin. And as soon as you have that, you can start reporting on it using the gadget you already successfully implemented. Or if that's not an option, I would consider building 2 filters; 1 for QA and 1 for Dev, displaying your bugs using 2 different gadgets and showing them by priority/status. You can even use a different color for the title bar of your gadgets to clearly indicate which is Dev and which is QA.
But that's something you will have to look into for yourself. I hope I managed to give you some pointers about how you can implement your original request and some leads on how you might improve the way you are managing your data currently.
As far as EazyBI is concerned; to offer your boss a daily overview of current bugs, I'm sure that might be overkill. I think you getting your data structured in such a way that they become easy to report on might be higher priority now. If in time you run into the need to do historical reporting (such as ('how many bugs were created vs resolved in each month of last year' and were they 'QA or Dev'), need the ability to plot those reports out nicely in different kinds of graphs, definitely have a look at it then.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Heya, Hipchat friends! We’re so happy you’re checking out Stride. Whether you know it or not, you have been instrumental in making Stride come to life. Every feature, design, and functionality...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs