JIRA Node Issue - Get Many vs Expand

Questions
1

Describe the problem/error/question

When using the JIRA node and the “Get Many” operations along with the expand option, it will cause an HTTP Failure

What is the error message (if any)?

Bad request - please check your parameters

Invalid request payload. Refer to the REST API documentation and try again.

Information on your n8n setup

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

I beleive the issue is that the JIRA API indicates it expects a string type for the expand paramter.

The code shows that it is being converted from a string to an array

if (options.expand) {
  if (typeof options.expand === 'string') {
	  body.expand = options.expand.split(',');
	} else {
	  body.expand = options.expand;
	}
}
2

Hey @spyder, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@darrell_tw, @tamy.santos, @jabbson - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

4

Hi @spyder

Please file a bug report. Include your version (2.36.7), the specific code snippet you found, and the error message. This will significantly speed up a fix by the core team.

5

Thanks @Lopez

I have already implemented this workaround as you described. I do prefer to use the native nodes of course when possible :+1:

6

Here’s the native version.

7

Hi @spyder ,

Great catch identifying the exact lines in the node source code.

As @Lopez pointed out, Atlassian changed the Jira Cloud search endpoint parameters to expect a single comma-separated string for expand instead of an array, which causes the native Jira node to fail when converting it.

Until the n8n core team patches the node parameter handling, switching to an HTTP Request node using your existing Jira credentials is the best immediate workaround.

Thanks!

8

New version n8n@2.39.0 got released which includes the GitHub PR 37527.