Contract bug in Jira Agile REST API

Hello, Atlassian!

I believe this is a bug, but since it isn’t critical or a security issue I’m reporting it via CDAC.

The Jira Agile REST API (JIRA Agile 7.0.4) states that a 204 (success) is returned when an issue is successfully moved to the specified sprint.

However, when I attempt to move a subtask to a sprint that is different from the parent issue sprint, the API call returns 204 even though the subtask doesn’t change. My expectation was that the call should return a 400 (invalid request).

1 Like