Jira Integration with Jira Spoke

[bekfro]

I seem to be having a connectin issue when setting up the Flow for Jira create issue.

I have the connection/credentials / API Token but when I create the flow I'm not getting the 

Credential alias filed to display so the project list will not populate:

Any ideas what I may be missing?

[SwarnadeepNandy]

Hello,

I am also having the exact same issue. But I have debugged it enough to find out that our ServiceNow instance is successfully connecting to the Jira instance. As part of the "Create Issue" action, ServiceNow is successfully placing a GET request to JIRA, but we are receiving error.

http status - 403

{"errorMessages":["The app is not installed on this instance."]}

We are working with our JIRA colleagues to figure out the issue once we have a solution. I can let you know.

But in the meantime, you can verify if it's the same error from JIRA side like mine or it's something else.

• Elevate Outbound http log levels to validate Outbound Http logs.
  • glide.outbound_http_log.override.level (type:String) - All
  • glide.outbound_http_log.override (type:true|false) - True
    If the properties are not present, please create them. Make sure to switch them off, when you finish debugging, it may generate heavy logs.
• Check Outbound Http Requests and verify if there is a request from ServiceNow to JIRA's url (api.atlassian.com).
• Click on the flow action to check if a GET request is triggered every time you click open "Create Issue" action.
• Check the Request and Response body for the log records.

FYI - If you are using OAuth and you are following ServiceNow documentation, there is a minute mistake (my assumption). In the documentation, it has been mentioned to keep Grant Type as Authorization Code, whereas for machine-to-machine interaction Grant type should be Client Credentials. So, if you are using OAuth and have not already changed it, make sure to modify the value.

Its NOT the field of Application Registry (Default Grant Type), but Grant Type field in the OAuth Entity profile used for Oauth 2.0 credentials. 

Edited:

Grant Type - Authorization Code seems to work fine. Only catch is you need to manually authenticate Jira using the UI Action "Get OAuth Token"  in the OAuth 2.0 Credentials form. This is a one time activity and going forward, access token will be reissued using refresh token.

Kind Regards,

Swarnadeep Nandy

[bekfro]

I actually opened a case with ServiceNow on this.  Apparently after San Diego, the connection alias field will no longer be presented, but as long as the next phase where you get the Project ID populates, your connection is there. 

[Trish Mac]

We're on Tokyo presently and the Connection Alias field is still there in the HTTP(s) Connection configurations.  I'm not sure if that's what you're referring to. 

[Trish Mac]

I had the exact same issue.  I reviewed my configurations and found that I didn't put my Jira password in the Jira credentials configuration.  Once I corrected that, I could see all the projects in a list under Project Key.  That might not be your issue but perhaps review your configurations.  I hope that helps.

--Trish