Skip to end of banner
Go to start of banner

Create Issue Matrices

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

On this page:

Create Issue Matrices

After installing the Issue Matrix for Jira Cloud app, you can go to your project’s setting in Jira Cloud and create matrices with configuration options set according to your needs. The configuration allows you to specify each matrix's context, issue types, and data.

The issue matrices are elements with context, type, and data that are visualized in Jira Cloud issues. You may check the Configuration options section in this document for more details on each option offered by Issue Matrix. 

You can create four different types of Issue Matrices:

You can create as many Issue Matrices as you like in different projects or issue types. To achieve it, navigate to your project’s settings in Jira Cloud and start creating Issue Matrices. Also, you can create one issue matrix and link it with multiple projects.

Issue Matrix lets you have completely different information in the issue views of the different projects. You need to create different Issue Matrix configurations for each project.

Visualization in issues

After creating an Issue Matrix with the configuration of your choice, a new panel will be visualized in the project’s issues with the configured data in it.

Configuration options

Each Issue Matrix configuration consists of the following sections with options: Context, Type, Data, and Sort By. You also need to name your matrix and optionally give it a description.

Context

The context options allow you to define the projects and the issue types where the particular Issue Matrix will be visible.
You can also customize the issue types where the Issue Matrix panel will be visualized. By default, the panel is visible in all issue types.

Linking Issue Matrices to projects

You can link a single Issue Matrix to multiple projects, and it will appear in all of them. Changes to multi-project matrix configurations affect all linked projects. Learn more about project linking

Selecting issue types for multi-project matrices

For matrices that are linked to multiple projects, you can select issue types per project. This means that the matrix panel will only be displayed for the issue types selected for a given project in the matrix configuration.

For example, let's say that you have a matrix linked to projects A and B. You've selected the issue type story from project A and task from project B in the Context > Issue Types sub-section. The matrix panel for project A will appear only in stories, while for project B the matrix panel will appear only in tasks.

Type

The options in this section allow you to choose the type of issues that it will contain based on the matrix type.

For Sub-task and Epic matrices, in the Type > Issue Types sub-section, you can choose the types of issues that will be displayed in matrix panel.

For multi-project matrices, you can select issue types from each project. A linked project’s matrix panel will contain only the issue types selected from that project in the configuration. Learn more about project linking

Suppose, there is a matrix linked to projects A and B, and in the Type > Issue Types sub-section and you’ve chosen issue type story from project A and task from project B. The matrix panel for project A will contain only stories, but the project B’s matrix will show only tasks.

Filter JQL option allows you to enter a JQL query in the configuration to filter further the issues displayed in the matrix panel.

Data

You have to choose columns, to create an Issue Matrix successfully. You can select most of the custom fields from your Jira Cloud instance and set them as columns in the Issue Matrix panel. Check the list of custom fields that have specifics in the implementation.

Issue Matrix for Jira Cloud allows you to customize the width of each column to achieve better overall visualization and alignment. You can specify the column width in pixels ("px") or as a percentage of the table width ("%"). Examples: 20px, 25%.

Visualizing long headers/column content

A column’s content may be larger than the column width set in the Issue Matrix configuration (either because of the header or the column content length, e.g., long words). In that case, the column in the Issue Matrix panel will be expanded and longer than the specified column width in the configuration.

Solution

The column width option works best when there is enough space for all the columns and their content. We recommend splitting a large Issue Matrix into two smaller ones with 4-5 columns each and configuring them to suit your needs. Learn more

When choosing a field for a column in the Issue Matrix panel, the column width is initially set to "Auto." "Auto" stands for automatic sizing, and the column width, in this case, is automatically determined by the browser. If you want to set the customized width of a column back to Auto, delete the contents of the Width field.

Sort By

Having issues ordered per your team’s needs is essential for productive work in Jira. 

In Issue Matrix, you can set a default order for the issues displayed in an Issue Matrix panel. Just choose one or more sortable columns in the Sort by section of the configuration. Only sortable fields are listed in the configuration.

Sort By and JQL Issue Matrices

Sort By option is not available in JQL matrices, and the default sort order may be specified via ORDER clauses in the JQL entry directly.

For example, you might choose the Summary and Status columns as a default sort order criteria. Then, after saving the Issue Matrix configuration and opening an issue, you’ll be able to see the issues in the Issue Matrix ordered accordingly.

Sort By and Filter JQL

If you set sorting criteria with the ORDER clause in the Filter JQL section, the Issue Matrix panel visualized in an issue will be empty.

To sort the data in your Sub-task, Epic or Issue Links matrices, use the Sort By option in the configuration.

  • No labels