/rest/issue/{issue}/execute doesn't seem to decode post parameters
I'm noticing that if I encode the post parameters, the update fails. However, when I don't encode the post parameters, things seem to work. Is this intentional?
Also, is there a reason that the rest interface seems to be so inconsistent? Here are some examples:
- create an issue => issue id returned via Location HTTP header
- query => issues returned as XML content in body
- update an issue => acknowledgement returned as plain text in body
Can I make a request in 4.0 that there's just 1 way for rest data to come back? Prerably as XML content.
Please sign in to leave a comment.
Another issue with the /rest/issue/{issue}/execute command is that it seems to want to lower case my input. So that FOO-123 becomes foo-123.
Dear Matt,
Issue parameter of execute command is case insensitive.
What library do you use to call YouTrack REST API?
No, there is no special reason but backward compatibility.
For me I have to include a second parameter for the execute to work.
Does not work (error 400)
Does work