I have updated my n8n cloud version to [email protected] and Jira issue creation is now failing. We need to downgrade to 1.91.3. How can we do it ?
This is the error:
The resource you are requesting could not be found
null for uri: https://eatic.domain.ofuscated/rest/api/2/search/jql
Thanks in advance
Hi @jalbert , welcome to n8n community!
I believe this issue is related to your question:
opened 05:30AM - 14 May 25 UTC
in linear
### Bug Description
Hi,
Iām encountering a regression in the JIRA node behavio⦠r since upgrading to n8n v1.92.2.
In version 1.92.2, a JIRA node that previously worked fine now throws a 404 error when executed. The same workflow works without any issues when I downgrade back to v1.90.2, so it appears something has changed in the newer version that breaks the JIRA node functionality.
Please let me know if you need more details ā Iād be happy to provide workflow examples or logs.
Thanks!
### To Reproduce
1. Open the workflow that uses the JIRA node
2. Run the workflow on n8n v1.92.2
3. Observe that the JIRA node returns a 404 Not Found error
4. Downgrade n8n to v1.90.2 and re-run the same workflow
5. Observe that it works correctly without any errors
### Expected behavior
The JIRA node should execute the API call successfully without returning a 404 error, as it did in version 1.90.2.
The workflow should complete without any issues when using the same JIRA credentials and configuration.
### Operating System
Rocky Linux release 8.8 (Green Obsidian) + podman
### n8n Version
1.92.2
### Node.js Version
20.19.0
### Database
PostgreSQL
### Execution mode
main (default)
Hopefully, it will be fixed soon
1 Like
Hi @mohamed3nan , we are running cloud version, so I think this workaround is not valid in our environment. Is there any other alternative option to wait bug could be fixed?