Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the appropriate product.
Atlassian JIRA Product Limitations
■ Optimized for the team centric use and management
■ 3rd party add-ons required for basic Quality Management features
■ Scaled Agile is not a built-in capability & only supported via Services partner.
■ No Concurrent user licensing (Only Named Users, which becomes expensive at scale)
■ Extra add-on’s needed for HA, Enterprise scalability, and Performance
■ Substantial Audit and compliance limitations when tracking field and record updates
■ Limited best-practice configuration for Agile implementations
■ Minimal roll-up visibility makes enterprise reporting difficult and time consuming
■ Restrictive project structure limits platform adaptability
ALM Octane Product Strengths
■ The only product that natively supports Waterfall, Hybrid, and Agile software development at enterprise scale with quality management built in.
■ Full Agile support at Team, Program & Portfolio level.
■ Native support for the most popular Agile frameworks
■ A unified, end to end lifecycle management platform with no dependencies on 3rd party components for core functionality.
■ Delivers comprehensive governance and compliance for mission critical systems.
■ Built to support Agile at enterprise scale, with out of the box integrations to Project Portfolio Management solutions, providing a “single source of truth”.
■ Comprehensive Data Analytics measure quality, identify change impact, and determine code coverage.
■ Scales seamlessly to support thousands of concurrent users, with no additional product fee for High Availability.
■ Flexible Licensing models including cost effective Concurrent Licensing in addition to Named users.
■ Packaged integrations with open source and third party solutions to support planning, build analytics, continuous quality, end to end traceability, and extensive reporting.
■ Customizable business flows and governance frameworks
■ Connections to Continuous Integration pipelines for real time application build quality.
■ Designed and built to scale for highly regulated large enterprises
My personal opinion:
If you are a startup/small company with small teams, Jira is your tool to go.
If you are a bigger company with enterprise processes, audits, certifications, various Agile trains, etc., Octane is your tool to go.
If you want to scale Agile, Octane is your tool to go.
I haven't tried Micro Focus ALM Octane. I have tried Jira and I like it.
I work at a healthcare company with 1000+ employees.
From a test planning and test management perspective, tracking requirements to tests, to defects, which one is the best tool and why: MS DevOps or Jira?
Thanks in advance for your assistance.
Azure DevOps generates a wiki report after executing pipelines for automation testing.
I need to simultaneously push and execute test cases in HP ALM. Each test case should have a unique id and be dynamically updated as soon as the pipeline is executed.
Has anyone tried to integrate Azure DevOps with HP ALM? If so, your tips and guidance will be much appreciated!