Custom JIRA Connector

[crhext]

Hey guys,

In my company we can’t leverage the built in JIRA connector as our JIRA server is behind a firewall so i can’t authenticate my account.

I am however able to access the REST API to directly enter issues into JIRA (using postman for example..). Are there any examples in this community of people using a custom connecter to connector to connect to JIRA server REST API? I have heard success stories but struggling to get it set up myself..

Thanks!

[v-alzhan-msft · Accepted solution]

Hi @crhext ,

You could take a try to achieve it use custom connector in Microsoft flow, looking forward to hear from you.

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

I am trying to do the same. I can get the API to create a JIRA ticket from POSTMAN using a cookie, not ideal as it doesn't persist. It also works from a .Net console app using basic auth, but I can't get that to work in the custom connector. I am currently looking at OAUTH2. I find the Atlassian documentation to be very hard to follow, might just be me though.

Tony 

[ghollingsworth]

I was able to recreate the current connector using an HTTP Post to the REST API and basic authentication. If you're on JIRA server the method actually adds some flexibility that never existed in the old JIRA Server connector (adding components, access to custom fields, etc...).

That being said, you need to be comfortable with JSON to get it working. If you need to pull data from the response (issue key, etc...), you can use the Parse JSON action on the response body (which I use to insert the issue key into emails generated later in the flow).

[crhext]

Thank you guys. I got it to work pretty easily by importing a postman collection.

[copro]

I am trying to do this same thing in Jira Cloud, not Server, to submit an issue to a project with has lots of custom fields. I worked through several easy to understand errors (date formats, field types, etc) and now find myself confronted with a very vague error:

["We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file."]

I worked with the most experienced administrator and we were not able to find a log that captured anything about the submission. Did you ever run across this particular error?

[ghollingsworth]

No, I didn't come across that error, sorry.

I did run into some issue with custom field types (though it sounds like you worked your way through those). That being said, I was working with JIRA server.

Wish I could be of more help.

[FaerchDK]

@ghollingsworth 

@crhext 

Can you share some screenshots of what you did?

I'm looking to do something similar, but don't have much experience with API's and Postman.

So it would help if I could see what you did and adjust it to my needs.