When using the JIRA Software Node in combination with the On Error “Continue (using error output)” option, the nodes does not actually follow the error output path when an error occurs
Hi there, did you solve this?
No, this was never resolved
Just to keep this topic fresh. This is still an outstanding issue in the latest version.
The JIRA Software node ALWAYS errors out the workflow despite setting it being configured to either “Continue” or “Continue (using error output) for it’s “On Error” configuration.
Hi there, thanks for bringing this up! I notified the team regarding this issue and created a ticket to make sure we get to it and fix it
Thanks for being part of the n8n community!
1 Like
Thanks @RomanDavydchuk !
Hoping to see this improved upon.
A couple other things i have noticed with the JIRA Node include:
1.) The “Continue on Error” doesn’t work (as mentioned in this ticket)
2.) There is no option for Batching requests (I have to use a combination of loop/wait nodes to avoid hitting JIRA rate limits when pushing a large number of requests to avoid rate limit failures.. which only makes the above issue worse when it won’t continue on error)
3.) If i set the node to retry-on-fail, and it is processing a batch of items, if any one of the items fails, it retries all incoming items from the start of the batch rather than just the failed items. This makes this feature unusable in combination with the above related issues all in some way related to error-handling.
Curious if we should expect a fix for this in an upcoming release?
Should i just move to using the HTTP Node with my own API calls instead of the catalog node?
Is this already fixed? I still have the same error on my workflow