Custom Graphs in JIRA dashboard

[Anthony Amirfar]

I got the request recently to put together a dashboard for our leadership team but I'm having quite a bit of trouble executing on this request. Any insight is welcomed! 

Here is the request:

• Chart 1 = Issues by Customer
  • X Axis = Customer Name
  • Y Axis = Stacked bar showing count of issues by severity (Critical, High, Medium, Low)
  • Interaction behavior = Clicking the bucket of issues by severity for a customer (e.g., Critical issues for Renteria) takes you to a list of those issues
• Chart 2 = Overall Customer Impact
  • X Axis = Issue Severities (Critical, High, Medium, Low)
  • Y Axis = Stacked bar showing count of issues for that severity by customer
  • Interaction behavior = Clicking the bucket of issues by severity for a customer (e.g., Critical issues for Renteria) takes you to a list of those issues
• Chart 3 = Issue Aging for Customer Tractors
  • X Axis = Age Ranges for <2 Days, 3-5 Days, 6-9 Days, 10-20 Days, 20+ Days
  • Y Axis = Stacked bar showing count of issues for that age range by severity (Critical, High, Medium, Low)
  • Interaction behavior = Clicking the bucket of issues by severity for an age range (e.g., Critical issues for 3-5 Days) takes you to a list of those issues
• Chart 4 = Issue Aging by Customer
  • X Axis = Age Ranges for <2 Days, 3-5 Days, 6-9 Days, 10-20 Days, 20+ Days
  • Y Axis = Stacked bar showing count of issues for that age range by severity (Critical, High, Medium, Low)
  • Filter = Customer Name
  • Interaction behavior = Clicking the bucket of issues by severity for an age range (e.g., Critical issues for 3-5 Days) takes you to a list of those issues
• Chart 5 = Tractors with Issues by Customer
  • X Axis = Last 4 digits of vehicle PIN
  • Y Axis = Stacked bar showing count of issues for that PIN by severity (Critical, High, Medium, Low)
  • Filter = Customer Name
  • Interaction behavior = Clicking the bucket of issues by severity for a PIN (e.g., Critical issues for PIN ending in 0025) takes you to a list of those issues

[Polina-DevAcrobats-]

Hello, @Anthony Amirfar 

Polina here, representing NaraSyst and our marketplace app, Performance Objectives: Charts for Jira. I truly believe that our app can assist you in creating the perfect graphs to meet the needs of your leadership team.

Chart 1: To create this chart, you have the flexibility to choose 'Reporter', 'Organization', or any other custom text field you use for 'Customer' as the x-axis. You can also visualize the count of issues by severity using stacked bars. With our app, the desired interaction behavior is available for all 5 charts that you need. Here's a sample visualization for this chart:

Chart 2: Similar to Chart 1, you can utilize 'Severity' (Priority) for the x-axis and 'Stack by' Reporter or Organization (Customer) for the y-axis. 

Chart 3: You can track the age of issues specific to customer tractors using the 'Time since' metric and customize the distribution slots to fit your needs, such as categorizing issues based on time since creation, e.g. "Time since created for all unresolved issues <2 Days, 3-5 Days, 6-9 Days, 10-20 Days, 20+ Days". Alternatively, you can explore the 'Time in status' metric to analyze the historic data of issue age.  

Chart 4: Building upon Chart 3, you have the same configuration options. Additionally, our app allows you to define custom data sources by selecting specific projects, filters, and applying various segmentation options like JQL, issue types, statuses, and more.

Chart 5: For this report, you can stack issues based on the last 4 digits of a custom field. With Automation, you can create a hidden custom field containing the last 4 digits of the Vehicle PIN. Our app seamlessly integrates with this custom field, allowing you to utilize it for the x-axis or 'Group by' / 'Stack by' options.  Please note that using Automation you will also have to populate the custom field - once for the historical data, and again this automation must be triggered by Issue Create/update for future data. 

As part of our upcoming roadmap, we plan to introduce the ability to "custom trim" text fields, eliminating the need for additional automation steps, so stay tuned for updates!

To help you evaluate our app, we offer a 30-day trial period. Our team is ready to assist you in configuring your custom reports, so feel free to reach out to us with any questions or for further assistance. 

Best,

Polina

[Emre Toptancı _OBSS_]

Hello @Anthony Amirfar

For Charts 3 and 4, our marketplace app can help you with some of your needs.

Our team at OBSS built Time in Status for this. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

   

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per Vertical or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

  

https://marketplace.atlassian.com/apps/1211756/

EmreT