![]() ![]() Our bread and butter is synchronising JIRA and HP ALM using Tasktop Sync. IntelliQA is a Certified Service Provider of Tasktop. I have used it to synchronise HP Agile Manager and HP ALM, and HP ALM to HP ALM, and found it a little cumbersome and the synchronisation period is too long (5 minutes). The ability to integrate with Jira is new for HP Synchronizer, and I haven’t used to the integrate the products. From looking at videos all these products look very similar in how they approach the same need. I am now at another company and will evaluate ConnectALL and Bridge as we simply must have flat pricing. I have also used ALM Sync but have heard of many limitation with this. Tasktop were very good to work with though and sincerley tried to create a solution that met our needs and was reasonably priced. There was also a concurrent license but that could only be used once every 4 hours which was therefore a terrible solution. There were solutions such as being able to re-use named licenses every 3 months but it would have been complicated to administer. 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). For example a user may create an incident in Jira (req in ALM) per day or every other year but you pay for each user anyway. They took a fee per user which for us was not viable as we had a high number of users creating few incidents. Functionally it gave us exactly what we needed (and we had fairly complex needs) but then (2014) the pricing was a nightmare. I used Tasktop Sync to integrate ALM and Jira for both requirements and defects. Please reach out to OpsHub’s Integration Experts for an initial free consultation on integration planning. OpsHub’s Commercial Edition additionally supports the integration of more advanced data and use cases. Customization of workflows and configurations is possible, too. It supports syncing of history, attachments, links, and comments. OpsHub’s free Community Edition can integrate standard entities between HP ALM and Jira, It supports the integration of the entities, Defects, Requirement Test Management Data, etc., from Micro Focus ALM to the entities, Bugs, User Stories, and Test Management Dara on Jira. ![]() When you integrate user fields like Assignee, Reporter, etc., if the username is not the same, understand whether mapping the users is done dynamically without mapping each user (one by one) or it will be manual mapping. As part of the evaluation, analyze which tool supports conflict management in such cases. If you are looking to integrate data bidirectionally, there is a possibility of data being updated simultaneously in HP ALM and Jira.Evaluate the volume of coordination effort among team members required for Sync Reliability and Completeness issues. Understand all data the tool can integrate, such as Defects (along with attachments, links, comments, mentions, and inline images) and test management, and the data that the tool cannot integrate.As part of the evaluation, analyze what part of integration may require script and involvement from your side. These can be highly time-consuming, error-prone, and can hinder operations. Some tools are a collection of unsupported beta versions of scripts, requiring a very high degree of sophistication.Understand whether an interface is to configure the integration of entities or if there needs to be coding/scripting required.I believe the following are the key must-have considerations as part of the selection criteria: To help you select the right integration approach and tool, you should first define your integration requirements and selection criteria. HP ALM and Jira can be easily integrated with the aid of a third-party Integration Solution. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |