The integration of HP ALM/QC with JIRA makes it easier for the development, and quality assurance (QA) teams to collaborate with each other.
This, in turn, helps in delivering a high quality product to customers at a faster pace.
HP ALM/QC JIRA Integration Overview
In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements.
Best-of-breed systems such as HP ALM/QC and JIRA bring rich functionalities to the ecosystem. By integrating HP ALM/QC and JIRA, enterprises can seamlessly manage the product development. The developers using JIRA will have clear visibility into the quality parameters and test results at all times. On the other hand, the QA team members will have real-time visibility into the codes being written and have full context of the development.
How HPQC – JIRA integration is beneficial for an enterprise
- Access to QA plans and defects in real time
- Real-time updates on the status of a story, its estimated time of delivery, and any risks that might delay the impending release
- Complete context of the customer requirement and visibility into codes written by the development team & test cases
written by QA team
- Coordinate on the delivery timelines seamlessly with concurrent updates on changes
With HP ALM/QC + JIRA integration, enterprises can:
How OpsHub Integration Manager integrates HP ALM/QC and Jama
OpsHub Integration Manager integrates HP ALM/QC and Jama bi-directionally. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All ‘requirements’ from Jama automatically synchronize to HP ALM/QC and all the defects associated with the ‘requirement’ synchronize back to Jama.
Popularly synchronized entities
Use Case: HP ALM/QC Integration with JIRA
Problem statement: The development team creates versions, sprints, and requirements in JIRA – which is the development system and replicate the same in HP ALM/QC – which is used by the QA team. The defects are created in HP ALM/QC and then replicated in JIRA. Manual replication of data takes a lot of time and effort.
Solution: When HP ALM/QC and JIRA are integrated, there will not be any duplication of efforts and the data between both the systems will synchronize in real time.
- The development team creates a ‘version’ in JIRA with basic attributes such as name, description, start date and end date. It synchronizes to HP ALM/QC as a ‘requirement’.
- The development team, then, creates ‘sprint’ in JIRA with basic attributes, which synchronizes to HP ALM/QC as a ‘cycle’.
- The development team then creates ‘requirements’ in the already created version and sprint in JIRA. The ‘requirements’ sync to HP ALM/QC with traceability of cycle and release.
- The developer then works on the requirement and updates the status of the ‘requirement’ to ‘closed’ in JIRA, which again synchronizes to status of the ‘requirement’ in HP ALM/QC.
- The QA team, then runs a quality test and finds a ‘defect’. They log the defect in HP ALM/QC, which synchronizes to JIRA.
Benefits of integration for HP ALM/QC and JIRA users
HP ALM/QC users
- Real-time updates on the story and associated changes/enhancements
- Access to the business requirements, development status, and associated updates from within HP ALM/QC
- No manual efforts needed to keep backend teams updated on the QA cycle and reports
- No duplication of efforts for entering the same data in multiple systems
- Clear visibility into quality parameters and test results in real time
- No dependency on manual communication for making business decisions