You can certainly use the two-dimensional gadget as indicated by @Vasiliy Zverev, but I would extend this answer a little bit.
Step 1 create a saved filter restricting to bugs for only those projects you are interested in.
Step 2 create a dashboard with appropriate gadgets installed to display the results of the stored filter from 1.
Now depending on your stakeholders and what they need to know you can add any dashboard gadget and show the information.
I tend to use pie/bar charts for non-technical stakeholders as they find these easier to interpret.
You can display multiple gadgets on the same dashboard to allow comparison across different projects for instance.
A key gadget I use when looking at the handling of bugs is the opened vs resolved gadget as this shows (with a suitable time period - normally 90 days) any trends in terms of how the bugs are being resolved.
In the end though it all comes down to what message is required for your stakeholders who are going to look at the report.
An extension to the above answer is that if you have Confluence you could embed the same gadgets in the page there but add more explanatory text around each gadget and also "pretty up" the display rather than be restricted to the limits of a JIRA dashboard.
Hope this helps and gives you some thoughts on how to do it.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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