| Table of Contents | ||||
|---|---|---|---|---|
|
| Excerpt | ||
|---|---|---|
| ||
 |
Overview
Teams have their own key insights for their Jira Software projects, agents need specific answers to be solved for their Jira Service Management queues, and so on and so forth. You could name more examples where a user need to perform a different query to search in Jira for relevant information. That’s why the Jira Query Language (JQL) was built for. It’s a powerful search based on clauses (field + operator + value) to return a list of issues, which for the sake of reuse, can be saved as filters. Projects in Jira require enough information to properly track their status and control a successful result. For doing so, Projectrak by DEISER provides a unique solution to add custom fields to projects, making data annotation a simple and smooth process. Review all the benefits that this app brings, like predefine fields ready right after installing it; the list view of projects to see your portfolio information at a glance; the release view to keep your version planning visible for all stakeholders, etc.
This gadget displays the result of a JQL PQL query or an existing filter, as a table or a chart. Select Indicate a predefined filter or a custom JQL Select filter or custom JQLcustom PQL, then indicate the how you want to display the results View Type, the Columns you want to display in your report in case of a table (drag and drop to change the order), and performing grouping and/or aggregations (see next sections for further information).
Projectrak provides the Project Query Language (PQL), which is like the Jira Query Language (JQL), but to query data from your projects.
For example, to list all the issues projects in the “Teams in Space” project (project = “TIS”) and still pending to do (status = "TO DO") sorted by CreationDate in descending order (ORDER BY created DESC) you’ll type the following JQL query
project = "TIS" AND status = "TO DO" ORDER BY created DESC
Get started with JQL or have a look to the Advanced Search to master queries in Jira
the software category where the Country is Germany or the Continent is Europe, then use the following PQL query:
category = development AND ( Country = Germany OR Continent = Europe )
You can select any of the following visual metaphors to represent the resulted data by the JQL in the View Type field: Table, line chart, tile chart, pie chart, bar chart, grouped bar chart, stacked bar chart or multi line chart.
...
View type: Table
The results of your JQL PQL query as a table, where you can select which columns are displayed.
...
Group results by selected columns If you are familiar with the GROUP BY statement in SQL, you’ll quickly find interesting uses to group the results of your JQLPQL. If you select to group the results by the previously selected columns, the result rows will be split into groups, based on their values. Thus, only one row will be displayed for each of the groups, so be careful because this implies constraints on the columns.
For example, if we filter the previous list of issues by the column Status, the results will show only two six rows , (one for the status To Do and other for the status Done.
...
And if we select these three columns: Status, Assignee and Project, the resulting list will display three rows like in the following image:
...
per status) vs one status per project row otherwise.
...
The grouping of columns is typically combined with aggregations, which moves us to the next section.
...
For example, if we want to calculate indicate the mean of the story points
...
total number of projects per status and lead:
...
View type: Chart
| Tip |
|---|
Remember that: Chart by. Indicates the x-axis values (horizontal axis), also referred as the series, or in layman terms, the concepts we see in the legend of the chart. Type. Is the aggregation you want to apply to the field: count, sum, max, min, mean. Check the aggregations section. Field. Indicates the y-axis values (vertical axis), what do we want to plot in the chart. |
Line chart
A line chart represents the results of your JQL query as a series of data points connected by a straight line. It’s common to visualize trends over periods of time or dates in the x-axis.
...
Multi line chart
This chart is a line chart with more than one line, which is useful when we need to compare data in a time series or trends.
...
Tile chart
This visual representation presents the information in a set of tiles. You can display the result of your JQL and apply aggregations. For example, you can display the number of request of each request type of your Jira Service Management support desk, or display the sum of all the original estimates of the assigned issues, by assignee.
...
Bar chart
A bar chart represents the results of your JQL query as a series of rectangular bars with the height proportional to the represented values. It’s useful to compare results of different types or categories.
For example, Chart by assignee, type count and field issues would display a chart where each assignee would display the number of assigned issues:
...
Grouped bar chart
We can perform more complex comparisons of the information returned by our JQL query by grouping by specific fields. In the previous example, we could add a Group by status, and we’d see the number of issues by assignee grouped by the issue status:
...
in |
...
the |
...
Stacked bar chart
...
chart |
...
. |
...
...
Pie chart
A pie chart is a visualization of your data in a circular graph, where each slice indicates the quantity of the result of your JQLPQL. When a pie chart has several sections or slices, it’s difficult to compare one with another. To overcome this inconvenience, the pie chart comes with a table indicating the values of each slice and the % it represents.
...
When the field selected in “Chart by” has a date format e.g., Created, a new selector appears to allow grouping by day, week, month, quarter or year, making the results easier to understand and communicate.
...
...
Custom colors
Colors have the power of communicating meaning, provoke emotions and highlight information. Within our organizations and teams, it’s common to associate concepts to specific colors, making easier and quicker the communication of ideas and information.Whenever you select a chart, you’ll be able to select In projects we give colors to priorities, status and logos, so a quick glance gives us enough information to transmit information, provoke reactions or prompt responses.
All charts display the ability of changing the color of each specific segment or value of it:
...
The provided color picker allows permits the selection of a color either colors by hexadecimal codecodes, RGB or our pre-defined 24 colors palette (selected based on the right contrasts and tones).
Hide segments
Not all the results are needed when communicating information in a chart, sometimes because one of those values or segments distorts the results or deviates the attention.
The silence, as well as the absence of elements are key to properly communicate information. It’s up to the ability of the chart creator to master this skill. We just give you the tools. Clicking on the 👁 eye icon, the corresponding segment is hidden (or shown) in the chart:
...
Reorder segments
In the same line of hiding segments or With a similar aim of customizing the colors of our charts, rearranging the position of the existing segments or values reinforces the way we transmit the information with our charts.Just drag and drop any segment or value or hiding segments, moving around the existing segments to new positions reinforces the message of the information we are transmitting to the target audience.
For doing so, drag and drop the segments or values from the six dots in the left side of the segments and move it , upwards or downwards, to the correct placenew position, and the chart will be updated accordingly.
...
Name your gadget meaningfully, so everyone knows at a glance what it is about and when to use it. Fill out the rest of the fields as applicable, namely:
The datasource, where the Confluence cloud instance select a Projectrack datasource, remember that you have to create this datasource first, to indicate where it is installed.
The JQL PQL (Jira Query Language) query or filter to filter the list of issues (see the JQL PQL documentation). If you don’t add any and the PQL field is empty and you click “Load”, all the gadget will request all the content in projects will be requested to the source instance, this might in case of very large instances, this could cause performance issues. We recommend to add adding at least one clause, for as an example, to list all the issues of the project Teams in Space use the clause
project = "TIS”. And remember that the gadget returns the results of the query, which are not fixed and could return all the projects with an End date and High or Blocker priority use the clause"Priority" IN ("High", "Blocker") AND "End date" is not empty. Worth mentioning that the result of a query is not fixed and can change over time.The View Type parameter to indicate the visual representation of the JQL PQL query results: Table, line chart, tile chart, pie chart, bar chart, grouped bar chart, stacked bar chart or multi line chart.
The Chart by parameter (just for charts) to select the x-axis value, in other words, what you see in the horizontal axis. These values or concepts are indicated in the chart legend.
The Type parameter (just for charts) to indicate what type of aggregation you want to apply to the field parameter: Count, sum, max, min, mean. Check the aggregations section.
The Field parameter (just for charts) to select the y-axis values (vertical axis), think of what you want to count (or any other aggregation) and plot in the chart.
The columns (just for the table view) that will appear in the list to display the search results. At least one column has to be present. Drag and drop to reorder the columns. Check the section.
Group results by selected columns (just for the table view) in case you want to group the results of the query by the previously selected columns. The resulting rows the result rows will be split intogroups, based on their values. Check the group results section.
The aggregations (just for the table view) in case you need to perform calculations -Count, sum, max, min, mean- over the results. Check the aggregations section.
Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration
Integrations
(see Jira Software cloud)- (see Jira Service Management cloud)
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
We are working on our growing catalog of Dashboard Gadgets: KPIs and Metrics and Dashboard Integrations: Supported Products, but contact us you want us to expedite a specific one, visit our Help Center.
...
This gadget is not included in any pre-defined dashboard, check other orphan gadgets: Orphan gadgets.
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
See also
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|