Tailor your Custom Charts for different audiences using Simple Search tabs
Tempo Team
Simple Search is a Jira gadget or Confluence macro that comes with Custom Charts for Jira and Custom Jira Charts for Confluence respectively. It enables fast, dynamic filtering on any Custom Chart it’s linked to. Frankly, it’s a flipping awesome feature for your charts because it allows users viewing them to easily drill into specific data points without having to edit the chart’s configuration.
The Simple Search gadget/macro and the Custom Charts gadget/macro are separate and have unique configuration settings, although the user interface and customization options are very similar. Adding the interactive searching capability of Simple Search to Custom Charts happens by:
Adding and configuring the Simple Search gadget/macro
Adding the Custom Charts gadget/macro and connecting it to the Simple Search gadget/macro. This involves:
Adding the Custom Charts gadget/macro
Setting the Simple Search gadget/macro as the Source on your Custom Charts gadget/macro
Configuring the Custom Charts gadget/macro
These steps are described in more detail in our documentation.
Using tabs to create different views for different audiences
Everybody cares about different things. Teams want to see the data that’s relevant to them, and the best way of getting them to focus on the right metrics is to not show them ones they don’t need. Enter the Tabs feature of Simple Search, which allows you to create different views for different audiences.
Let’s say that we have 3 audiences who each care about different information in our Jira Service Management project called Support:
The entire support team, who need a general view of everything that’s being worked on
Becky, an individual agent on the support team
Alex, a support team supervisor who needs to pay attention to her team’s tickets
In Custom Charts, you can use the Tabs feature to save dynamic searches that will display specific data points for each of these audiences.
Here’s how it’s done…
Configuring Simple Search
We’ll start with the same base of information for all 3 audiences. This could be your saved Jira filter, “All Open Support Tickets”, which includes all unresolved tickets in your Support project. First, set this as the Source of Simple Search in the Simple Search editor.
Next, click the TABS toggle to enable the feature. The first tab that you see, Tab 1, will serve as the default view for anyone viewing the Jira dashboard or Confluence page.
So, let’s start by tweaking the default view to make it more suitable for the support team.
Support team’s tab
The support team cares about a general overview of all open tickets in the Support project. They’d like to be able to filter items based on priority to determine what they should focus on. To enable them to do this:
Rename “Tab 1” to “Support Team View”. Click the Pencil icon next to “Tab 1”, type the new name in the text box, and hit Enter to save the name.
Add fields relevant to the support team. We will keep things pretty general to accommodate all support team members. Add the following Simple Search fields to this tab by clicking + Add a field / Add another field on the right side of the editor under Simple Search Fields.
Status
Assignee
Request Type
Reporter
Created
Priority
Now, let’s move on to the next tab – we don’t need to save the gadget until we’ve added all of our tabs.
Becky’s tab
Becky is most concerned with high-priority bugs in the project that are assigned to her. To give her a good insight into these issues:
Add a new tab for Becky in the editor. Click the + ” next to the the Support Team View tab you’ve just made to add the new tab. Then rename “Tab 2” to “Becky’s View” like we did above.
Add the relevant Simple Search fields to this view. As mentioned above, Becky cares the most about her top-priority bugs. So let’s add the following fields:
Issue Type
Assignee
Priority
Status
You’ll then need to configure these fields to automatically show data points relevant to Becky. In the Live Preview on the left side of Simple Search, click on the following fields and select these options in each dropdown:
Issue Type
Select Bug
Assignee
Select Becky
Priority
Select Highest, High (use the “OR” operator at the bottom of the dropdown to include tickets that have either priority)
Your second tab is done! Now, let’s move on to the final configuration.
Alex’s tab
Alex is a supervisor on the support team who manages Becky and Morgan. She is most curious about their tickets, especially those that have been escalated. To provide her with a good insight into this data:
Add a new tab for Alex in the Simple Search editor. Click the “ + ” next to “Becky’s View” to add the new tab and rename to “Alex’s View”.
Add and configure the following Simple Search fields. Since Alex cares the most about issues escalated today for her team members, we want to make sure that we’re including those issues.
Issue Type
Assignee
Select Becky , Morgan (ensure the “OR” operator is selected at the bottom of the dropdown to include both assignees)
Priority
Custom JQL toggle (select this from the + Add another field dropdown or just use the + Add Custom JQL toggle button)
Add the following Jira Query Language (JQL):
status = Escalated AND status changed to Escalated AFTER startOfWeek()
Rename the Custom JQL field “Escalated Support Issues” using the “Name” box
Now you can click Insert to lock in all your Simple Search configurations and insert it onto your page or dashboard.
Once you have created your 3 tabs and inserted Simple Search, link Simple Search to a Custom Chart by setting it as the Source of the gadget or chart (more info on how to do that here).
Voila! Now, when the support team, Becky, and Alex navigate to their Jira dashboard or Confluence page, they can utilize their specific tabs to see the data they’re most interested in transform into beautiful charts.
See below for the end result of using the Simple Search gadget with the 3 tabs to create targeted charts for the 3 audiences.
Sign up for a demo
Register