Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

call to subtask/move fails with 400 Bad Request

George Actovia February 23, 2023

Hello,

 

On an issues list

https://[domain]/issues/?filter=[some_id]

We would like to be able to drag&drop issues to set priorities

 

When dropping an issue, a call is made to 

https://[domain]/rest/api/2/issue/[issue_number]/subtask/move

payload is

{"original":1,"current":0}

 

Response is 400 Bad Request and, obviously, if we refresh the page the order is the old one.

 

Please help us investigate this further.

2 answers

0 votes
George Actovia February 24, 2023

Here is a picture of what is happening

0 votes
Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 24, 2023

Hello @George Actovia 

There is no such endpoint:

https://[domain]/rest/api/2/issue/[issue_number]/subtask/move

hence the error.

Refer to the v2 REST API documentation

George Actovia February 24, 2023

But it not something that i have created. It's the endpoint that the Jira front-end is calling.

George Actovia February 24, 2023

I noticed this by using Inspector 

Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 24, 2023

Huh? Are you saying the front end is sending a request to an API endpoint and generating a 400 bad request error itself?

Or are you saying you're trying to interact with Jira's RESTRICTED INTERNAL APIs, which of course you aren't allowed to do, instead of the public APIs?

George Actovia February 24, 2023

The front end is sending these requests.

We are just trying to drag&drop stuff and we noticed it does not save if we refresh the page.

Then i looked at the inspector and i saw that that call is failing.

Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 24, 2023

Sorry, I don't think I can be of any further assistance, as I can't work out what it is you are claiming is happening and what is making it happen... you or the 'front end'.

Good luck with your 'investigation'

George Actovia February 24, 2023

here is a screenshot of what is happening

 

jira_drag_drop.JPG

George Actovia February 26, 2023

@Sunny Ape does the screenshot make sense to you?

Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2023

@George Actovia 

Nope, not one bit.

That screen grab is of the advanced issue search page in the UI. You said you want to "drag&drop issues to set priorities" but dragging and dropping issues on that page will do absolutely nothing to change the issues' priorities at all. Nothing. Zero. Zilch. Zip. Nada.

It seems to me you have just stumbled upon a bit of abstract, non-functional code that has absolutely nothing whatsoever to do with some non-existent 'drag&drop' functionality you think that page should have.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events