Dev Space

Customize & extend the power of Alteryx. SDKs, APIs, custom tools, and more!
The Expert Exam is now live online! Read about the specifics and what it took to bring it to life in the blog by our very own Elizabeth Bonnell!
SOLVED

JIRA Connector

Highlighted
8 - Asteroid

Thanks Tom,

Really appreciate you sharing your solution.
This is a really impactful contribution.

You are helping a lot of people with this one.

 

Thanks again

Gregg

Highlighted
7 - Meteor

Thanks this is really helpful, I am able to build python code for same

Highlighted
Alteryx Certified Partner

Hi All,

 

I just submitted this connector for a new API and added worklog download function.

https://gallery.alteryx.com/#!app/JIRA-Connector-/5de07bdf826fd30fa06e2f3a

 

For existing function, I simply modified REST API reference from "/rest/api/latest" to "/rest/api/2"

 

Thanks, Taylor. And please feel free to improve this macro.

Highlighted
5 - Atom

Hi,

 

Thanks for sharing this. Are you able to share this workflow? I'm getting a "The field schema for the output [Output Name] changed between iterations" error and don't understand why.

Highlighted
5 - Atom

Hi,

 

Thanks for all the info in setting up the JIRA connector.

 

When I ran the workflow with the URL and my credentials, I got the following error:

 

Error: JIRA Connector (1): Tool #227: JIRA API error --> HTTP/1.1 404

 

rrana_0-1599840039818.png

 

 

Any idea what could be causing it?


Thanks

Highlighted
6 - Meteoroid

I have been running the Jira Connector successfully for some time now and just last week began getting the same error message as above.

 

Error: JIRA Connector (145): Tool #229: JIRA API error --> HTTP/1.1 403

 

Does anyone know what would suddenly cause this?

 

Thanks,

Highlighted
5 - Atom

Hi Darrin, I had my issue resolved. Try checking the URL you are entering for the JIRA site - it should end in .com (without any extended links at the end of it). Please let us know if this helps resolve. Thanks

Highlighted
6 - Meteoroid

Thanks @rrana , but that is not the issue.

 

Come to find out it had to do with a password change and needing to log back in via the browser to get past the captcha.