This site is moving soon to become part of an integrated Appfire documentation and information site for our apps. This site will remain available during the transition to our new and improved site. Once this site is moved over, this banner will be updated with the new site link for easy access.

Take a look here! If you have any questions please email support@appfire.com

Agile Teams

A solution to Jira Cloud UI’s limitations for agile teams

One of the defining principles behind Issue Matrix for Jira Cloud is enhancing the existing capabilities of Jira Cloud to accommodate the needs of agile teams to access and work with actionable data without the need to navigate through multiple UI pages and waste valuable time.

While Jira Software is the most comprehensive platform for agile teams, a few UI flaws prevent users from utilizing its full potential.

Issue Matrix for Jira Cloud improves the Jira issue views and makes the issues easier to read. The app allows users to see additional information from subtasks or linked issues ordered semantically in a separate Issue Matrix panel. As a result, there is no need to open each subtask or linked issues individually to assemble the whole picture, saving teams many click-throughs and improving their daily work routines.

Teams achieve a genuinely agile experience, save time, increase productivity, and maximize their Jira investment.

Jira Cloud default visualization of sub-tasks in issues

Let’s look into how Jira visualizes subtasks in issues:

  • The description of the panel Subtasks is generic and not specific to the process used in this project.

  • A small icon identifies the type of issues: Development, Quality Assurance, or Documentation task.

  • There aren't column headers that explain the data in the columns.

  • Custom field data from other issues cannot be visualized in this view.

You can see what the default issue view in Jira Software looks like in the picture below.

Drawbacks of out-of-the-box Jira UI

The Issue Matrix app lets you overcome the following Jira UI’s drawbacks:

  • Lack of visibility into sub-tasks & linked issues
    Important information confined in sub-tasks or linked issues is neither intuitive nor readily accessible and requires users to open each issue individually to get the full picture separately.

  • Inability to understand displayed information

    The lack of column headers prevents users from semantically understanding the displayed information.

  • Inflexible configurations

    Jira doesn’t allow users to configure different views for different issue types or projects, thus stagnating how teams organize their projects.

Fine-tune your agile practices with Issue Matrix

Issue Matrix for Jira Cloud is designed by a team of agile product developers using Jira who want to improve some of its usability shortcomings. The app is easily integrated with Jira Cloud’s agile environment and allows users to enhance their issue view screen by adding information from other issues. All this data is available on a single screen, so users don’t need to open each issue individually.

Visualization of sub-tasks in issues with Issue Matrix

  • A user-friendly and customizable panel name. It’s the name of the Issue Matrix configuration you create in the project settings.

  • Customizable column headers with additional information like subtask summary, status, assignee, category, etc.

  • You can set a default sort order for the data in the Issue Matrix panel.

With Issue Matrix for Jira Cloud, Agile teams can easily overcome the limitations of their default Jira Cloud visualization - the tool is highly customizable. It significantly improves the usability, structure, and content display of sub-tasks, linked issues, and issues in epics.

Better visibility into sub-tasks & linked issues

To customize your issue views in the best possible way, we’ve developed four different Issue Matrix for Jira Cloud types. They allow you to define which issues and which issue fields (system and custom) will be displayed on the issue view screen.

This flexibility in configuration customization will enable Agile teams to reconfigure how and what type of information is displayed based on the users' needs.

Issue Matrix types

  • Sub-task matrices show subtasks of the current issue.

  • Issue Links matrices show issues linked to the current issue.

  • Epic matrices show issues linked to the current Epic issue.

  • JQL matrices show issues returned by a custom JQL query.

Learn how to create and configure different Issue Matrix types.

Content features for better flexibility & information display

Issue Matrix has a set of essential options related to the content of the Issue Matrix panel. When creating an Issue Matrix in a project’s settings, you can configure a subset of the settings below to apply to the panel visualized in an issue:

  • Types - You can define which issues will be included in the Issue Matrix table for each type.

  • Context - You can define different issue views for different projects and issue types.

  • Columns - You can choose the columns you want to include in the Issue Matrix table and set headers and width for the columns.

  • Inline Editing - You can enable inline editing for any field in the Issue Matrix table.

  • Sort By - You can define sort order criteria for the Issue Matrix table.

  • Filter JQL - You can apply additional filtering to the issues in your Matrix mode.

Learn more about the options for creating an Issue Matrix

See an example matrix configuration in a software development project below.

Advanced JQL Contextual Linking

Another invaluable feature for agile teams is the advanced contextual linking, which allows users to compare issue fields with the values stored in the currently viewed issue. For example, users can quickly identify all issues in a given project that only share a common value, such as:

  • System field examples: Reporter, Assignee, Component, Fix version, Status, etc.

  • Custom field examples: Customer request type, Multi-group picker, Text field, etc.

This extension to the JQL syntax can be used in JQL-type Issue Matrices and the JQL filter configuration option in the Sub-Task, Issue Links, and Epic Issue Matrices. 

Learn more about our JQL extension

Use inline editing for enhanced productivity

Inline editing allows users to update issues within an Issue Matrix panel quickly. This feature allows users to make immediate changes to many issues at hand without leaving the current page.

For instance, you can update the estimates of all subtasks in an Issue Matrix panel without leaving the current issue and opening each issue individually.

You can update the Jira fields like SummaryStatusAssignee, etc., directly in the Issue Matrix panel. For the complete list of editable fields, visit our documentation about the inline editing capabilities Issue Matrix for Jira Cloud offers.

Enhance your agile boards with Issue Matrix

The Issue Matrix panels are visualized in Jira’s project boards too. You can significantly improve how your Scrum and Kanban teams interact with the tasks on their project boards by using Issue Matrix’s features like contextual linking and inline editing.

The Issue Matrix panel is visualized by default on boards, thus eliminating the need for additional click-throughs. Once you configure and enable an Issue Matrix panel in a project, the panel will be visible on the issue views and boards in the project.

 

Issue Matrix in Scrum boards

You can see the Issue Matrix panel on a Scrum board in the following picture.

 

Issue Matrices in Kanban boards

You can see the Issue Matrix panel on a Kanban board in the following picture.