HPE ALM and JIRA Integration: What Real Users are Asking

At IT Central Station, 6,680 users follow the category of ALM reviews and questions published by enterprise tech professionals. Since the beginning of 2017, our ALM reviews have been viewed over 21,890 times.

Krunal Rajendra Akojwar, Testing Manager at a manufacturing company with 1,001-5,000 employees, asked the following question to our ALM Suites user community:

Read Krunal’s full Q&A here.

What Did Users Respond to Krunal?

Various users from the IT Central Station community share their experiences with the integration process between HPE ALM and JIRA, discussing topics such as:

• Collaboration with their dev teams

• Data synchronization between HPE ALM and JIRA

• Planned PoCs of the synchronization

• Pricing models for integration tools

• Customer support

Ramash Karanam, Microsoft and Dev-ops Architect at Mphasis:

“I have integrated TFS 2013 and HPE ALM to transfer the defects between the two entities. Clients are using HPE ALM for defect management. They test the product and raise a defect on HPE ALM. development team using TFS for their development.

This integration helps the management to move/sync the bugs from HPE ALM tool to TFS and assign the defects to dev. team. This synchronization is scheduled on weekly basis. This integration went well and it is currently live.”

Rob Smit, Agile Consultant at a Financial Services Firm with 1,000-5,000 Employees:

“Synchronizing data between JIRA and HPE ALM is one thing. I think TaskTop and ConnectALL and all other tools can do the trick.

In the coming weeks, we will do some PoC's to prove the sync. I am worried about something else though: to use the data in ALM, we need relations (like test coverage, requirement traceability, linked entities defects).

I think that after every synchronization, these relations have to be added manually. This will be unacceptable for the users, I'm afraid.

Does anyone have experiences to share with us?

So I am not worried the existing links will disappear, I am worried that the NEW requirements, defects et cetera won't have any links. That means a lot of manual effort after every sync…”

Matthew Lapsley, Co-Founder at a Communications Service Provider:

“I used Tasktop Sync to integrate HPE ALM and JIRA for both requirements and defects...

As we had 5000+ JIRA users and high churn of users (many consultants), the pricing got out of control (cheaper but not as good to enter data twice). There were solutions such as being able to reuse named licenses every 3 months but it would have been complicated to administer...Tasktop were very good to work with, though, and sincerely tried to create a solution that met our needs and was reasonably priced. I have also used ALM Sync, but have heard of many limitations with this.”

Zabrina (Staton) Martinson, Sr. Consultant - Enterprise QA/Agile Transformation at a Transportation Company with 1,001-5,000 employees:

“We are embarking on an integration with HPE ALM 12.5 & JIRA and are evaluating products now.

We used the Go2Group product at one point because it presented security vulnerabilities. And we just found out that the HPE ALM sync product does not offer a "many to one" sync capability to intake multiple JIRA containers into a single and HPE ALM project/release. So now we are looking at a product by Orasi, to see if it will meet our needs.

We are currently working on setting up a PoC to originate a defect in HPE ALM, send it to JIRA, have the developer fix it/provide a status update, and for that status to be sent back to HPE ALM. So within the next 3-4 weeks, we will know more.”

Read more user feedback on ALM suites:

• Users compare JIRA with other ALM solutions

• Users compare HPE ALM with other ALM solutions

• Our full collection of ALM reviews