Looking for Starter Kits? Head to the Community Gallery! Now formatted as YXIs for easy installation.

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Creating JIRA stories from Alteryx

5 - Atom

I just installed the JIRA connector to Alteryx (per links below):



Is there a way for me to have Alteryx create JIRA stories when certain conditions are met? For example, if a data review fails, then I want to create a JIRA story so that our technical team can investigate the discrepancy. Thanks!

Alteryx Alumni (Retired)

Hi @amichel,


JIRA not being natively supported by Alteryx -except through Download tool- I would suggest to contact the developer of the connector directly through this page: https://community.alteryx.com/t5/Data-Sources/JIRA-Connector/m-p/51562


Kind regards,


Paul Noirel

Customer Support Engineer

9 - Comet

I realize this is way after the fact, but the JIRA Connector on the Public Gallery cannot create issues.  However this does not mean that it is not possible.  Using the Download Tool you can utilize the JIRA REST API to create new issues, or update existing issues.  I have a working example of this, but am working with my employee to publish what I have built. 

8 - Asteroid

Hi Brian! Did you ever end up posting an example of this? I'm very interested in seeing how it works. Thanks!

9 - Comet

I am sorry, but my company policy does not allow me to post my workflow.


I can give you some advice though.

  1. Using a tool like POSTMAN is very helpful for testing API's and getting information about your JIRA instance
  2. Understand what fields can be created.  This is specific to your project and issue type.  Use the following API with a GET command to see the issue types and the fields that are available.  This will also show you what fields are required and what fields have specific values that need to be populated:
    1. https://<JIRA Server>/rest/api/2/issue/createmeta?projectKeys=<Project Key>&expand=projects.issuetypes.field
  3. Start simple with creating a Story IssueType with only the required fields and build from there.

Data Stream into Download tool:

  • JSON - This will be the "payload" containing the data that you want to load into the new story
    • Sample Payload for creating Story:

      {"fields":{"description":"As an Alteryx Developer I want to contribute to the community","issuetype":{"name":"Story"},"project":{"key":"XXX"},"summary":"Test Story Title","labels":["Dev_Test"],"duedate":"2020-04-24"}}

  • authorization - Base64 encoded string (see attached b64 Encode.PNG)
  • URI - the server and endpoint (https://myjiraserver.company.net/jira1/rest/api/2/issue)

I have also attached captures of the config for each of the 3 tabs in the download tool.  Given the information above you can plug in JSON, authorization, and URI into a text input tool, pass that to a download tool with the same configuration as my pictures, and you should be able to create your story.  Beyond that it is really just data manipulation to get the information you need into the JSON string to create more complication stories or issue types.


Good luck!


8 - Asteroid

Hi @bkclaw113 ,


Can you please elaborate a little on the Base64 encoding and the process that is shown in the screenshot. I already have an API key created from JIRA itself. Can I not use the API key directly as a password and pass that to the header of download tool ?


Thanks in advance!


9 - Comet

It has been a long time since I looked at the documentation but I believe that the JIRA API's only use an API key if you are connecting to JIRA from another Atlassian product called confluence. All other connections use basic authentication which is combining the username and password with a colon, and then using the B64 Encode tool to encode that string, then prepending the word Basic followed by a space before that B64 encoded string.


So start with username and password coming from whatever source

Formula Tool creates new field called "Auth String" from formula: [username] + ":" + [password]

B64 Encode Tool with the input field mapped to [Auth String] (this will output a new field called [base64_encoded])

Then another Formula tool to create a new field called "Authorization" from formula: "Basic " + [base64_encoded]).


Now you have a field called "Authorization" that can be assed to JIRA API via the Header in the Alteryx download tool.


Hope this helps.

8 - Asteroid

Thank you! It definitely made things a lot clearer. However, when I follow this process I am getting the response as HTTP connection established which is good but what I am now not sure about is that is it how the workflow is supposed to behave. Should I not be getting or seeing my JIRA stories when I open JIRA Project to check if a story has been created. At the moment I cannot see any new story created using Alteryx in JIRA. It puzzles me a little. 


Looking for your valuable advice on this!



8 - Asteroid

Hi @bkclaw113 ,


I tried your method but I am getting this error. I am really not sure what to make of this since I am using the password and B64 encoded password as well. I am attaching the error message here. Please let me know if you are familiar with this error and how to resolve this.




Error: Message (10): JIRA API error --> HTTP/1.1 200 Connection Established
Proxy-Agent: Zscaler/6.1

HTTP/1.1 401
Date: Mon, 07 Feb 2022 14:31:31 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000;includeSubDomains
X-AREQUESTID: 931x15627124x1
Referrer-Policy: strict-origin-when-cross-origin
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: ALLOW-FROM https://jira.XYZ.com/
Content-Security-Policy: sandbox
Strict-Transport-Security: max-age=31536000
Content-Encoding: gzip
Vary: User-Agent
Content-Type: application/json;charset=UTF-8
Content-Length: 75