We're Adding Even More Standard Reports

The stacked bar chart is based on two different fields: series and category.

Th series are represented with colors that are stacked in each bar, and the bars themselves are the category field. Together, the report shows the number of each series within every category and the total category count.

The example above is showing priority as the category. Each bar represents a priority from lowest to highest and each color represents the number of issues from a specified source like email or phone with that priority. At a glance, you can see which priority you have the most of and in that priority category, which are your biggest sources of issues.

To generate the report, you have to specify a series field, in this case source, and a category field, in this case priority. You also have to give it a project key, display values, and specify the types of issues to include. There are some additional optional fields to enhance your report, like the ability to add custom JQL.

As with all standard reports, the expanded view offers you more detail. You can see the exact count from each source with a given priority and the links will take you to the issues in Jira.

In a grouped bar chart, you can compare multiple sets of data where the colors help you see the same series across multiple sets. The series of bars are clustered in categories. It's a different way of looking at the same data from the stacked bar chart.

Here, because the series are represented as bars in parallel instead of stacked, you can more easily eyeball which series is responsible for a bigger count. It's really easy to see that customers are your biggest source of issues in most categories.

This bar chart is the same as a regular stacked bar chart except the chart is turned 90 degrees so the bars appear horizontal.

A donut chart is a variation of a pie chart. It's a circular graph that is divided into slices to help visualize proportions or what percentage of a whole any data set represents.

For example, you could see an issue count by component for your project. To generate the report, you just need to specify a project key, the field to include and the issue types. You can also just show unresolved issues like with other standard reports in VisualScript's collection.

And as with other standard reports, we give you the option to add JQL filtering for some advanced work, but it's not required to create a report.

A funnel report shows you values or counts across multiple stages. For example, for your service desk, it can show the count of issues by status. Since this is a standard report, you can choose from the standard list of field types like Priority, Component, Issue Type, Resolution, and so on. These reports are flexible.

In the example below, we created a report that shows incident issue types by their status: closed, open, work in progress, or pending.

The expanded view lets you see the exact count of issues in each status along with a percentage of the whole they represent.

A bubble timeline report can show you events in chronological order. Our report lets you see the number of tickets per event using the criteria entered in the parameters. For example, you may want to see a timeline of bugs entered or incidents with issues. In the field parameter, you can choose any date field to include created, updated, resolved, or even a custom field. Make sure you specify a project key and optionally specify the types of issues you want to include.

Next you will want to decide what to count for each event: issues, story points, original estimate, remaining estimate, or time spent.

Similar to the bubble timeline, the block timeline also shows a timeline of events and the number of tickets per events based on the criteria you specify in the parameters.

In addition to the events and ticket counts, the report lets you group your data in swimlanes based on any field in Jira. For example, in the report below we grouped our events by priority.

A standard grid report lets you see your data based on two axis. For example, status and priority. Priority from low to high can be show on the Y-axis, while status from open to closed can be shown across the X-axis. The shapes on the grid will represent issues that meet those two criteria. In the shape that represents the issue, you can choose what information to display like source, urgency, and so on.

The update now lets you switch your grid from the existing "shape" mode where you have individual issues represented as cards on your grid to an issue count style grid.

In the Issue Count version of the grid report, you'll simply see a number for the issues that match both parameters along the two axis. For example, you'll note that you have 6 issues that are both open and high priority and 4 issues that both pending and medium priority.