n8n-io / n8n

Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
https://n8n.io
Other
45.95k stars 6.46k forks source link

Radio Buttons Customfield not being set-able in JIRA Data Centre #8070

Open itsmichaelk opened 9 months ago

itsmichaelk commented 9 months ago

Describe the bug We have an issueType where there is a required customfield called 'Severity of impact' and it's type is 'Radio Buttons'. When I now want to create a JIRA ticket in n8n and try to set this field, I get 'ERROR: Bad request - please check your parameters ' all the time.

To Reproduce Bildschirmfoto 2023-12-18 um 10 42 20 This is the customfield selection.

I now set the customfield like this: Bildschirmfoto 2023-12-18 um 10 44 44 First I gathered an example issue via REST API to see what JIRA is responding. customfield_13101: {"self": "https://jira.ORGANIZATION.cloud/rest/api/2/customFieldOption/11701", "value": "Medium (needs to be fixed soon)", "id": "11701", "disabled": false}

Therefore I tried these values: 11701 "id":11701 "id":"11701" "value":"Medium (needs to be fixed soon)" {{ [{"id":"11701"}] }} {{ [ {"self": "https://jira.ORGANIZATION.cloud/rest/api/2/customFieldOption/11701", "value": "Medium (needs to be fixed soon)", "id": "11701", "disabled": false} ] }}

But nothing is working. I keep getting this: Bildschirmfoto 2023-12-18 um 10 47 08

Expected behavior I want n8n to be able to set the radio button custimfield's value.

Environment (please complete the following information):

Joffcom commented 8 months ago

Hey @itsmichaelk,

Thanks for the report, It looks like JIra is returning an error to say it isn't happy with the ID or the value you are sending. I will need to spend some time looking at the Jira API docs to work out what to send as it looks like it might want the ID of radio button to be sent in a special format.

itsmichaelk commented 7 months ago

Any update on this? :)

Joffcom commented 7 months ago

Hey @itsmichaelk,

I did take a look and oddly I couldn't see anything documented but I did see other users outside of n8n having the same issue.

What I will do to make sure I don't forget is make a dev ticket so we can handle this properly instead of needing to use an expression.