Jira get all issues node is shwoing: Bad request - please check your parameters

Questions
1

I have created API token in jira using my admin account and used the same credentials to setup jira. I want to extract all the issues from active sprint. But every time i execute node all i get is: Bad request - please check your parameters.

Please find the screenshot for the reference:

image
image1295Ă—525 46.2 KB

Any help will be appreciated. Thanks in advance.

2

Hey @zeta_pashupati,
Welcome to the Community,

For this node, Jira already expects a Sprint ID/Board context, and mixing the wrong operation/params often triggers the generic 400 Bad request.
Do this instead:

  1. Make sure you’re using the Jira Software node operation that matches sprint issues (Get Sprint Issues) and that it has the required inputs:
    • Board ID (the board the sprint belongs to)
    • Sprint ID (the active sprint id you already have, 2 in your screenshot)
  2. Don’t use a plain project JQL here. Use one of these:
    • No JQL at all (recomended first): let “Get Sprint Issues” return everything from that sprint.
    • Or if you want filtering, use sprint JQL like:

    • sprint = {{$json.sprintId}}

    • or sprint in openSprints() AND project = SCRUM

      1. Most common cause of 400 here: wrong ID type People often pass a sprint number/name instead of the numeric sprint id from Agile API. In your case, confirm the sprint id you split is the actual id returned by “List sprints / Get active sprints”, not originBoardId or sequence.

      If you remove the JQL and just pass Board ID + Sprint ID, it should work.

3

hi @zeta_pashupati
I would replace the current JQL with a valid Jira query such as project = SCRUM AND sprint = {{ $json.sprintId }} (or at least project = SCRUM), because in n8n the Jira Get Many operation filters issues via JQL and the value shown in your screenshot (project “SCRUM”) is not valid JQL syntax, which is why Jira returns Bad request - please check your parameters.

4

Hey @Mayank1024 and @tamy.santos ,

Thank you so much for your suggestion. I have tried both of your suggestions, but still doesn’t work for me. I assume there is some issues with the node itself, That’s why i used HTTP node and this work like a charm.

5

Http node always saving the day! :rofl: