Hi All - We have test cases, defects in HP ALM and would like to migrate to Jira. The project follows Agile sprints.
Can you please suggest what version of Jira and Plug ins are needed to migrate test cases and Defects into Jira.
Also Since the Jira will be brand new, cna we migrate the data from ALM as it is . and then reconfigure Jira with new workflow.
Thank you! Sashi
There's no particular version of JIRA that matters for importing data from there. You mention "Agile", so I'd recommend JIRA Software over plain JIRA, and I'd quite simply say the latest version.
You are talking about test cases and defects. That's fine, but you need to think about how you are going to represent and use them in JIRA. HP and JIRA do not have the same data structures, so you're going to need to be converting from HP into a format suitable for JIRA.
JIRA itself does not really have support for testing either. You can rig up plans and cases, treating them as issues, but most of us find that a bit weak. Most testers reach for JIRA add-ons to help them with testing, and I would strongly recommend you do the same, because the better add-ons understand test plans, repeat runs, regression and so-on in ways that JIRA does not.
I've seen several used with JIRA (X-Ray, SynapseRT and QMetry) but only really been involved when it was Zephyr, Testrail or Kanoah (I want to tell you that work with one them now too, in the interests of openness). They are all different, and my experience with all of them is too shallow to tell you which one might be best for you. Have a look through https://marketplace.atlassian.com/search?product=jira&query=test
You are also going to need to think about how you change the test data from ALM into the right shape for them.
HP ALM actually has a built-in bridge that allows for an easy integration; however, you will have to map a number of fields to JIRA and if your projects have different workflows you will have to map each project accordingly.
Custom fields in JIRA require additional configuration as they may appear initially as read-only fields if the mapping is done by someone other than a JIRA admin. Administrators of JIRA should be able to create read-write fields without incident.
We are currently using JIRA Cloud and HP ALM v 12.2.
I replied to a post from another user asking about simialar things, so you may find some of this info useful. Agreed with Nic that the stock CSV importer is really all you need. The part of JIRA that does this type of import is the JIRA Importers Plugin or JIM for short. A lot of enhancements have been made to it in the past couple years, so I would definitely use a modern version of JIRA.
HP ALM has a built-in synchronizer that bridges the tool with JIRA; therefore, no other tool is needed. You may run into some configuration quarrels when mapping the two; therefore, ensure that a JIRA administrator is driving the integration to prevent any blockers. Non-administrators of JIRA may find that custom fields are "R" (read) only vs RW (read-write) when mapped.
If you are using an older version of HP ALM you want to consider ConnectAll or something if the sort.
I've attached a link that provides a demonstration of the integration between HP ALM and JIRA Cloud.
Can you help how to do mapping between the HP and Jira. Also we do not have any projects yet created in jira, so how should we proceed?
Should we create projects in Jira first?
ALM has many statuses which we dont want in Jira, so how to map 10 Statuses to 5 statuses in Jira
PLease share any documentation
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs