-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single Digit IssueTypeID in JIRA causes an ERROR - Not a valid Jira Issue Type ID - JIRA Cloud #8560
Comments
Hey @mathiasdaniel, What happens if you select the issue type from the dropdown box does that work? |
Hey @Joffcom, good advice, but there is also a Problem:
|
Hey @mathiasdaniel, Can you configure an HTP Request node to use the same credential and set the URL to It can also fail to load if the project id isn't correct as an example for my test project which is the first project in my jira instance the id is Task - 10001 Don't forget that these are IDs internal to Jira, I would be very surprised if you had single digit IDs on Jira Cloud. |
@Joffcom we are also surprised of one digit IssueTypeIDs - after the migration from jira server to jira Cloud. |
Hey @mathiasdaniel, Can you try the request option I provided so we can see what Jira is replying with? |
Hey @Joffcom I changed the Method to Here is the Output:
With the IssueType Problem (issueTypeID 10302) i am able to create a JIRA Ticket via the native JIRA Node. BTW: I searched the Web for the Schema Description for the issueTypeID, in the end chatgtp tells me a Range of 1 to 10 digits, type number. |
Hey @mathiasdaniel, Yeah we were expecting higher so we need to change that regex, I am not sure why it isn't loading the list though. I will update that regex though and we can see if it changes anything. |
@Joffcom thank you so much. n8n and the community are awesome. |
@mathiasdaniel if I was to make a test image based on the PR above would you be able to give it a go in a test environment? |
Hey @Joffcom sure, we only need the Release Tag for the docker build, at the moment we use latest. Thx. |
@mathiasdaniel docker tag is |
Hey @Joffcom , we builded a test instance and tested the following execuions with the JIRA node: JIRA Node, IssueType, select by ID 3 works - JIRA Ticket is created, JIRA Node Ouptut is fine as expected Thank you for your help |
Hey @mathiasdaniel, Perfect, in that case I will get the PR ready for review and we can look at merging it for the next release. |
Hey @mathiasdaniel, The change for this has been merged and will be generally available in the next release. For now I will get this closed. |
Fix got released with |
Describe the bug
This Bug causes when you try to create a JIRA Ticket with the JIRA Node.
In our case we are using JIRA Cloud, before switching to JIRA Cloud we used JIRA on premise and there was no problem at all.
With JIRA on premise the IssueTypeID was five digits long, example 10003. This works, with JIRA Cloud a IssueTypeID with only one digit, example 3 fails.
If you put a single digit IssueTypeID, Example 3, into the IssueTypeID Form Field, there will be an Error when an JIRA Ticket should be created by the JIRA NODE.
In Detail:
a single digit IssueTypeID as fixed Value is not allowed, Error via regex check:
if you ship the IssueTypeID as JS Element as expression, it generates an error after the execution:
if you ship the IssueTypeID as number as expression, it generates an error after the execution, also invalid URL:
To Reproduce
Bild an Workflow with one Start and one JIRA nodes direkt in Line.
After the execusion of the JIRA node with the Create Operation and Issue Ressource you will recieve this error(s).
Environment:
OS: Docker
n8n Version 1.26.0
Operation mode : own
Has anyone a suggestion how we could fix this thing?
THX
.
The text was updated successfully, but these errors were encountered: