
Drive your Jira visualization to a new level with powerful features for Sub-Tasks, Linked Issues, Stories in Epics
Drive your Jira visualization to a new level with powerful features for Sub-Tasks, Linked Issues, Stories in Epics
Drive your Jira visualization to a new level with powerful features for Sub-Tasks, Linked Issues, Stories in Epics
Better visualize your sub-tasks, linked issues, or issues in Epic by adding extra fields filtered by your needs. Improve your organization by tracking the progress of all completed, currently running, or to-do issues.
Get greater visibility into additional information and fields about each sub-task, linked issue, or Issues in Epics without opening it individually and save hours of pointless clicking.
Both system and custom fields can be visualized as a column of sub-tasks, linked issues, or Stories in Epics, without the need to open them individually. Issues with the same semantics can be grouped in a separate panel.
Better visualize your sub-tasks, linked issues, or issues in Epic by adding extra fields filtered by your needs. Find, modify, and easily extend the configuration options, choose locations, or configure actions.
The enhanced visibility, flexible configuration, and the ability to perform immediate changes to the issues save your team hours while keeping their productivity and improving the workflow.
Bring context to your Service Desk requests by utilizing an advanced JQL syntax designed to filter a list of related, yet not directly linked requests based on your system.
Better visualize your sub-tasks, linked issues, or issues in Epic by adding extra fields filtered by your needs. Find, modify, and easily extend the configuration options, choose locations, or configure actions.
The enhanced visibility, flexible configuration, and the ability to perform immediate changes to the issues save your team hours while keeping their productivity and improving the workflow.
Bring context to your Service Desk requests by utilizing an advanced JQL syntax designed to filter a list of related, yet not directly linked requests based on your system.
More details
- Greater Sub-Tasks Details:
It gives you additional information and fields about each sub-task without the need to open it individually. Sub-tasks can be broken down by type. You can also add user-friendly and easy-to-configure panel names. It helps teams to visualize better the tasks they are responsible for.
- Effortless & Error-Free Creation of Related Issues:
Easily create relations between objects in an error-free way. You can create issues in Epic or Sub-task in issue - the choice is yours.
- Better Visibility of Issues in Epics:
Improves the visibility of the User Stories and other issues linked to Epics by adding information about story points, teams, x versions, etc.
Need help? Ask us for a Demo or Support.
Appfire helps great makers build what's next. Our growing portfolio of apps empowers teams worldwide with workflow automation, business intelligence, and administration at scale.
More details
Issue Matrix helps both technical & business users overcome Jira's default visualization limitations & provides vast enhancement of the main Jira screen.
Fine-tune your Agile practices: Issue Matrix table content improves how users interact with tasks on their Scrum & Kanban boards.
Five different modes: Sub-Task, Issue Links, Epic, Filter, & JQL.
Content features for better flexibility & information display: a subset of settings like modes, columns, sorting, categories, or create & link actions.
Issue categorization: identify issues based on specific criteria & represent them via colors.
Advanced JQL contextual linking: compare issue fields with the values stored in the currently viewed issue.
Quickly edit Service Desk fields without navigating away from the current page.
Appfire helps great makers build what's next. Our growing portfolio of apps empowers teams worldwide with workflow automation, business intelligence, and administration at scale.
More details
Issue Matrix helps both technical & business users overcome Jira's default visualization limitations & provides vast enhancement of the main Jira screen.
Fine-tune your Agile practices: Issue Matrix table content improves how users interact with tasks on their Scrum & Kanban boards.
Five different modes: Sub-Task, Issue Links, Epic, Filter, & JQL.
Content features for better flexibility & information display: a subset of settings like modes, columns, sorting, categories, or create & link actions.
Issue categorization: identify issues based on specific criteria & represent them via colors.
Advanced JQL contextual linking: compare issue fields with the values stored in the currently viewed issue.
Quickly edit Service Desk fields without navigating away from the current page.
Appfire helps great makers build what's next. Our growing portfolio of apps empowers teams worldwide with workflow automation, business intelligence, and administration at scale.
Reviews for cloud
(34)Sign in to write a review


Reviews for server
(34)Sign in to write a review


Hi Yana,
Issue Matix for Jira Server is showing the sub-tasks as they are stored in Jira. The app does not store any information that may be “lost” during a CSV import.
The only recommended way for seamless export-import of issues is via Configuration Manager for Jira. We are not recommending the usage of the built-in export in Jira.
If you have any technical difficulties or concerns regarding the usage of Issue Matrix, you are always welcome to open a support request: http://support.botronsoft.com
Best,


Thank you, Fabio,
The Issue Matrix Team is grateful for your feedback and support!
Reviews for Data Center
(34)Sign in to write a review



Cloud Pricing
Server Pricing
Data Center Pricing
10 users$10 | 25 users$240 | 50 users$480 | 100 users$720 | 250 users$1,200 | 500 & upAdditional pricing details |
50 users$480/year | 100 users$720/year | 250 users$1,200/year | 500 users$2,000/year | 750 users$2,150/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does cloud app pricing work?
Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my cloud pricing?
Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.
The pricing structure for cloud apps is as follows:
- Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.
- Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
- Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
Annual subscriptions may offer a discount depending on the number of users purchased.
- Do you offer academic, community, or open-source licenses for cloud apps?
Yes. Academic, community, and open source licenses are available to qualifying organizations. See our Purchasing & Licensing FAQ for more information.
- Can I extend my free trial?
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
Botron Atlassian Apps (an Appfire company) provides support for this app.
Botron Atlassian Apps (an Appfire company) provides support for this app.
Botron Atlassian Apps (an Appfire company) provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2020-10-23
Summary
Next gen project support and minor bug fixes
Details
Versions
Version 3.3.12 • Jira Server 7.2.0 - 8.14.1 • Released 2020-11-11
Summary
Bug fixes
Details
Versions
Version 3.3.12 • Jira Data Center 7.2.0 - 8.14.1 • Released 2020-11-11
Summary
Bug fixes
Details
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Issue Matrix via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Issue Matrix. You're prompted to log into MyAtlassian. Issue Matrix begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Issue Matrix versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Find new apps or Find new add-ons screen loads.
- Locate Issue Matrix.
- Click Free trial to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Issue Matrix via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Issue Matrix. You're prompted to log into MyAtlassian. Issue Matrix begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Issue Matrix versions compatible with your instance, you can look through our version history page.