Director of Product at Indian Institute of Management Bangalore
Real User
Top 5
Jul 18, 2024
I would like to see some improvements in Adaptive Test Management for Jira. First, having a recommendation engine or feature that guides handling risks more intuitively rather than relying on manual processes would be helpful. Second, enhancing the connectivity with third-party tools like Teams or Slack would be valuable. One challenge with integrating Adaptavist Test Management for Jira into workflows is ensuring it accurately tags and incorporates all relevant stories and epics. Sometimes, it’s unclear if the tool considers all dependencies and backlog items, which can affect how risks are assessed. However, it sometimes seems to miss this high-level perspective, which can be a limitation based on how the product is designed. This has been a concern for those who use it regularly, although I don’t manage these aspects personally.
They should improve the solution's granular reporting feature. It could be more intuitive. It doesn't serve delivery and management purpose. They should integrate the solution with AI. So that, in case of test failures, it will help us know the reason instead of debugging the history of the test. The tool should automatically indicate the reasons for failure. It will save a lot of time.
Manager, Quality Assurance Engineering at a tech services company with 10,001+ employees
Real User
Mar 15, 2020
For now, the queries are not well integrated into the rest of Jira. They use a different syntax so you have to change how you present queries when you're looking at test cases versus everything else. Firstly, I would like to see the query capability integrated into the base query of Jira so I can query test cases the same way I query anything else in Jira. The second feature I would like to see is more visual gadgets that go on a dashboard, little pie charts and bar charts and histograms. There's a limited number now and I'd like to see more of them.
Something that needs to improve, is the model of the licensing. For instance, if you have two packs from two servers, you need buy two licenses. That doesn't make sense. I would also like to have more integration.
I plan to make some tests stand for my view, where I will want to play with the API to start to implement some of the tests because the is the plan to use it as main debt management system. Previously, we used a quality center from IBM but it was old technology. The main point that I want to get from this solution is to integrate this after a test run of the test and see results on JIRA, not on the CI system. When they need to provide some lab reports, of course, we can use a separate solution but business users, product owners will not be able to use it. They don't need such technical details, they need an open task in JIRA to check what failed what passed. We also want it to improve the sync. I don't like that you need to use a lot of tabs. One test case takes 15-20 minutes and on Zephyr is take about 5-10 minutes. They should shorten the time it takes by not using many tabs. There should be more customization abilities. One of my teams can need to create about a hundred test cases and they will need to spend twice time than with Zephyr. The estimation for creating this case will be increased twofold compared to Zephyr.
Learn what your peers think about Adaptavist Test Management for Jira. Get advice and tips from experienced pros sharing their opinions. Updated: May 2026.
Adaptavist Test Management for Jira delivers comprehensive test management capabilities with features for step reuse, test case repositories, and risk tracking, enhancing project management through sophisticated metrics and flexible configurations.Adaptavist Test Management for Jira integrates Microsoft services, offering a repository for test cases and supporting automation tools. Users benefit from risk metrics and flexible configurations for specific project requirements. Enhanced...
I would like to see some improvements in Adaptive Test Management for Jira. First, having a recommendation engine or feature that guides handling risks more intuitively rather than relying on manual processes would be helpful. Second, enhancing the connectivity with third-party tools like Teams or Slack would be valuable. One challenge with integrating Adaptavist Test Management for Jira into workflows is ensuring it accurately tags and incorporates all relevant stories and epics. Sometimes, it’s unclear if the tool considers all dependencies and backlog items, which can affect how risks are assessed. However, it sometimes seems to miss this high-level perspective, which can be a limitation based on how the product is designed. This has been a concern for those who use it regularly, although I don’t manage these aspects personally.
They should improve the solution's granular reporting feature. It could be more intuitive. It doesn't serve delivery and management purpose. They should integrate the solution with AI. So that, in case of test failures, it will help us know the reason instead of debugging the history of the test. The tool should automatically indicate the reasons for failure. It will save a lot of time.
For now, the queries are not well integrated into the rest of Jira. They use a different syntax so you have to change how you present queries when you're looking at test cases versus everything else. Firstly, I would like to see the query capability integrated into the base query of Jira so I can query test cases the same way I query anything else in Jira. The second feature I would like to see is more visual gadgets that go on a dashboard, little pie charts and bar charts and histograms. There's a limited number now and I'd like to see more of them.
Something that needs to improve, is the model of the licensing. For instance, if you have two packs from two servers, you need buy two licenses. That doesn't make sense. I would also like to have more integration.
I plan to make some tests stand for my view, where I will want to play with the API to start to implement some of the tests because the is the plan to use it as main debt management system. Previously, we used a quality center from IBM but it was old technology. The main point that I want to get from this solution is to integrate this after a test run of the test and see results on JIRA, not on the CI system. When they need to provide some lab reports, of course, we can use a separate solution but business users, product owners will not be able to use it. They don't need such technical details, they need an open task in JIRA to check what failed what passed. We also want it to improve the sync. I don't like that you need to use a lot of tabs. One test case takes 15-20 minutes and on Zephyr is take about 5-10 minutes. They should shorten the time it takes by not using many tabs. There should be more customization abilities. One of my teams can need to create about a hundred test cases and they will need to spend twice time than with Zephyr. The estimation for creating this case will be increased twofold compared to Zephyr.