JIRA cloud node => Create issue does not work

Questions
1

Describe the problem/error/question

In its most basic form, I have created a workflow that attemps to create a jira ticket on JIRA cloud. For this, I have installed a JIRA node.

th eproblem is that it does not give a list of projects, neither list of issue types. I have manually filled them in and still the node generates error.

Credentials are good because the same ones are used with another node “Get Issue status” and it all works well.

I have spent a few hours here and there with no success. I would be grateful to any help or orientation

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hey @phonitel2

Try making a custom HTTP Request to the Jira API and see what you get.

Let’s find out if this issue is related to the Jira node.

To build the request you can ask ChatGPT for the request:

  • method
  • URL
  • Headers
  • Body
3

Dear @solomon , thank you so much. Unfortunately, I am not this technical to create a http request. My idea is to use the JIRA node on Jira Cloud with API key. I have validated each component individually. In other words:

  1. When using the “get issue” node of JIRA with same credentials => It works => Credentials are correct;
  2. From there, the node does not display the project even manually => I guess the node has an issue.
    I would be grateful if it works for anyone. I have made 4 different installations ( dockers, npm based and it all yields to same issue and result).

I have activated the log with high log level, but it does not show low level calls to identify the issue.

4

In the meantime, for referene to any future user. There is a short workaround ,it is to use the project ID ( numeric number and not to confuse with the key ID). In my case, I could figure out that project ID to work on is a number such as 10004 and Issue Type ID is not to confuse with Issue type key id : it is a pur enumeric number. From there, it did the trick for now. However I would be grateful if the select box ( drop box) would work to make it error prone

1 Like
5

That’s great to know, @phonitel2

Unfortunately automations are still very technical.
n8n is a tool made for technical people.

But using custom HTTP Request to query the APIs is a skill you can learn in just a few weeks of deep work.

The HTTP Request node is essential in many n8n workflows and you’ll be surprised as to how many possibilities it opens up for you.

:muscle: Keep it up and don’t hesitate to ask the community when you need further help.

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.