Relationships Custom import not working, help appreciated

Richard Brown

I am struggling with an issue where I am unable to import relationships using the 'custom import' feature using the 'ImportRelationships' plugin with a .csv file. I don't get any error-message, but the import stops very soon after clicking on the 'import' button and no relationships are created. I have checked everything I know to check and have tried a few tests but am running out of ideas. I have read and re-read the documentation and searched the forum but so far have not found anything that helps. Does anyone have any suggestions?

Here's what I have tried so far:

• I am able to MANUALLY create a relationship between two items in the project
• I have verified that the relationship RULES for the project include the relationship I am trying to create
• I have tested the same import PLUGIN in another project which uses the same relationship rule set as the one I am struggling with (with same item types), it worked :-)
• For the record, I have double-checked the api-id's of the parent & child item types in the Plugin Params:
  parentType=137;childType=138;parentField=documentKey;childField=documentKey
• I have also double-checked the Plugin Class string : com.jamasoftware.contour.plugin.jama.ImportRelationships
• I have tried using both with a .csv file created using excel (based on source-data exported from jama) and with a simple 'one-liner' .csv created manually in notepad.
• There are 168 rows in the .csv file. I have tried deleting rows to only include fewer entries.
• I have previously performed the same import task a handful of times. The last few times were without hiccups, so I am a little surprised that it's not working now. I do remember struggling the very first time I tried, but I don't remember what I did to resolve the block.
• This is my first attempt to import relationships in this particular project. Could it be something with the way the project is configured?
• I have one theory: I may have tried to do the relationships-import once before checking that the selected relationship ruleset for the project did actually include the items & relationship I was trying to import. I don't remember exactly, but it is all correct now, at least. I have tried changing the relationship rules a couple of times since then. Could this be enough to 'flag' the project in a way that blocks further import attempts?

I am running out of ideas and patience. I find it a little frustrating that there is no error-message or logfile that could help me find the source of the issue. I have considered starting over and creating a new project from scratch , but I'm worried that I'll meet the same issue again.

Any tips would be greatly appreciated!

Richard Brown

PS I have also checked that the .csv file only includes valid 'documentKey' values which are comma-separated, and I am selecting 'Comma' as the field-delimiter in the custom-import dialog-box. I leave the 'optional encoding' field empty. I'm using Microsoft Edge on a Windows laptop with no browser-extensions installed.

Richard Brown

Here is a sample from my .csv file (which seems to get auto-formatted as a table when pasting here)

P326-BRx-22	P326-SYSRQx-90
P326-BRx-21	P326-SYSRQx-91
P326-BRx-22	P326-SYSRQx-91

Philip Schlesinger

@Richard Brown you appear to be missing the required semi-colon after the last field entry, i.e. it should be:

parentType=137;childType=138;parentField=documentKey;childField=documentKey;

Richard Brown

@Philip Schlesinger Thanks for responding! 😊 & well spotted! I checked this field in the plugin config and the semi-colon is not missing there, so I guess it was just a mistake when I copied the text into this discussion. My bad! As I wrote in the third bullet-point, the plugin worked correctly in another project, so my main suspicion was that the project I was trying to import to had in some way become corrupted.

Richard Brown

As an update to this issue: I ended up resorting to a workaround which was to create a new project and repeat the import process there. It worked without any issues, so I guess the problem was in some way linked to my original project. I did get some help from Jama Software Support, but we were sadly not able to find the root-cause of the problem. An error-message or debug-log might have helped.