Highlighted
Seelenbohrer
New Member.
1037 views

HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

I want to synchonize from HP ALM QC 12.5 to JIRA. I installed the HP tool "HP ALM Synchronizer Client 12.53.0".

I create a new Link from HP ALM (Entity Name: Requirement) to JIRA (Epic as Requirement).
I did the suptype mapping between "Functional Requirements - Epic"
I use an HP-ALM filter "A" to synchronize specific requirements with an specific value for a field named "required for".

I added one "functional requirement" in a HP-ALM folder (ReqID 752).
In HP-ALM, the filter "A" shows the requirement, and also the folder with an special icon (prohibition sign with filter icon). For me, it looks like that the folder is not filtered, but visible to show, where are the filtered items are located.

If I run the synchronization, it failed:
First error is, the folder is consider by the HP ALM Synchronizer Client and following error text is reported in the log file: Execution log file

04/18/2017,12:34:10,055 INFO (Create.From1To2.Source-FOLDER__752) : Input values: {Description = <empty string> Name = [PLAYGROUND]}  
04/18/2017,12:34:10,070 ERROR (Create.From1To2.Source-FOLDER__752) Create: threw an exception,skipping this entity and moving to the next, exception:The 'All issues' synchronization mode does not support issue in folder creation facility

I don't understand, why "All isues" synchronization mode is set, because, the entity is set as "Epic as requirement" ?
I don't understand, why the folder is consider, because it is not inside of the filter?
I know, that inside of the manual is a note regarding the folders: "Folders are automatically mapped if they contain a requirement type that is mapped. They cannot be configured. ".

Synchronization run continous also with this second error. HP-ALM Requirement (Req-ID 2809) is mapped correct, but it failes at the end also with following failure:Execution log file

04/18/2017,12:34:10,305 ERROR (Update.From1To2.Source-2809) Update parents: threw an exception,skipping this entity and moving to the next, exception:server.Execution.UNKNOWN_PARENT : The parent (id FOLDER__752) of the entity being synchronized is not mapped, or the hierarchical relationship is invalid. 

In the subtype mapping, I cannot find the folder parents. I also cannot find any options, do disable the parent field.

How can be synchronizised the HP-ALM Requirements without consider of the folder structure?

To set an alternate root folder is also no option, because we use the folders to get a structure for the requirements.

In Jira, there are no folders available and we don't want to use there folders.

Alternative: What is expected by HP ALM Synchronizer Client from JIRA, to pass the create.form for a folder?

 

Tags (3)
0 Likes
6 Replies
Raluca Popa
New Member.

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

Hi Seelenbohrer,

Did you receive any response to your problem? 

I tried to synchronize a requirement from ALM to Jira and during the synhcronization I got the first error like yours. The first error I have is:

Create: threw an exception,skipping this entity and moving to the next, exception:The 'All issues' synchronization mode does not support issue in folder creation facility

 

Then I am rendered 3 times the error below:

Create: threw an exception,skipping this entity and moving to the next, exception:server.Execution.UNKNOWN_PARENT : The parent entity (id FOLDER__1) is not mapped or unsupported in sub-type mapping, please check it.

I tried to map Requirement to Bug, just to test it works. I choosed this mapping because Defect (from ALM) to Bug (in Jira) worked just fine and I was expecting this to work as well.

Unfortunately that didn't happen, despite the integrity check successfully passed.

 

So, did you find any response/solution for your first error during the syncronization?

 

Thanks.

0 Likes
Seelenbohrer
New Member.

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

 I got no feedback.

For me, it is a easy change for HP to remove this "parent ID" during synchronization. But I looks like they have no interest.

0 Likes
jkf0407 Contributor.
Contributor.

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

I don't know if this will help but I am successfully running several requirement links and I always use the alternate root folder option as opposed to just dumping all requirements on the root of the module.  I create the folder requirements\epic\2018epic and I sync the pertinent epic requirements to that folder.  This way if I set up a link to sync issue type "story" then I will sync them to the folder requirements\story\story2018. Using this method, I have never seen the errors that you are reporting.  It's almost like you need to use the alternate folder option so that the synchronizer will know where to find the files in your filter.

0 Likes
Established Member.. evho
Established Member..

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

Hi, I am trying to achieve exactly what the original question describes (using the same versions of the tools).

I want to be able to have different Folders in ALM for the Requirements, instead of having to 'dump' them all in the Root folder.

From your reply (creating a folder called "requirements\epic\2018epic" and using it as alternate folder) I get the impression that you are still limited by having to put all requirements in this folder in ALM. I.e. You don't have the possibility to have different folders/hiearchy of folders in the same sync link between ALM and JIRA?

Is that correct?

BR,

Eva

0 Likes
Established Member.. evho
Established Member..

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

Hi,

I just received a response from Micro Focus Support:

Since in user guide (12.60), hierarchy in requirement for RTC and JIRA is not supported at all.

All the requirements has to be put under ROOT.

 

But I found a work around, and that is to create your own requirement type to represent the 'Folder', You can even use the same icon as the built-in 'Folder' requirement type. So in ALM it looks exactly as you are using the built-in 'Folder' type. I can now create the requirements (e.g. Stories etc) under our own 'Folders'.

In the synchronizer client I did a sub-type mapping for our own 'Folder'-type, and I choose to map it to 'Epic' in JIRA, which makes some kind of sense.

BR,

Eva

0 Likes
Seelenbohrer
New Member.

Re: HP ALM Synchronizer Client: Requirements synchronization failed to JIRA regarding HP ALM folder

Hi Eva,

thanks for this information.

I will try it. But what I not understand, where is the difference between the own req type and the "folder" type? Both contain a req_id and therefore the "parent" is also given.

And yes, it make sence to collect the requirements inside an EPIC.

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.