Error on ServiceNow Jira Integration using the Integration Hub

[Johannes Mweli]

Hi ServiceNow Community Developers,

I am working on a ServiceNow Jira integration and I am using the integration hub to achieve that functionality. Initially my integration was working fine in our Sandbox instance but then we upgraded our Sandbox instance which was on San Diego by cloning it from prod which is on the Utah version. I therefore had to rebuild my flow designer since it got wiped out by the clone. Since then my integration is now throwing a funny error which I am unable to track down to figure out it’s root cause.

I have attached the screenshots of what I see in the logs for the error that I am getting.

I have also attached the screenshot of the code that I use to populate the Issue in flow designer.

Would you please advise as to what could be causing this issue and what I can I try to do in order to overcome it.

Thanks,

Johannes

[Soufian AZZA]

Hello Johannes 

Did you found a solution to that problem, I have the same issue.

Thanks

[Georgi Yordano1]

It's hard to determine from the pictures what exactly is happening. 

But what can be seen is the following: The action "Get types of all fields" fails with an error. The error is stating that in the code execution this was evaluated: "undefined.issuetypes" or "var a; a.issueTypes" 

Looking at the "Document preview of ServiceNow Jira Integration error.PNG" picture, it's clear that the input of the action is an empty "issue" object.. I feel like something before those steps went wrong...

Have you tried creating the flow from scratch, or did you try modifying the existing flow which was created on the older release?

[Johannes Mweli]

Yes I was able to fix this and my integration is now in production and it is working fine. The problem was caused by the way I was populating the issue type, I was using the actual project name to populate the issue type instead of using the project key. You need to make sure that your Service account credentials are working correctly and that you know the key of project you are connecting to in Jira.

[Johannes Mweli]

Correction on the email I just sent above - meant to say "The problem was caused by the way I was populating the Project key" - was using actual project name instead of the project key. See "Create jira issue" screenshot I just attached. I am scripting the populations for the fields since I need to dynamically pick them however the main thing is to make sure you are using a project key that Jira recognizes.