Issue Summary

When jira.permission.scheduleissue.denied property is set to one status in the workflow, it blocks the possibility to reorder issues (“rank”) on the board and backlog as also the possibility to edit Due Date field. However, we are able to move the issue to an Active Sprint although Jira shows the following error:

This error is the same that is shown when reordering issues in the Backlog. However, for this action, the property indeed blocks the action, making the issue return to its original place.

Steps to Reproduce

1. Apply jira.permission.scheduleissue.denied (property key) / true (property value) to a specific status in the workflow
2. Go to the project backlog
3. Drag and drop to the active sprint an issue which current status is the one to which property above was applied
4. The error message will appear ("You do not have permission to rank...") but the issue will stay in the Active Sprint
5. If you refresh the page, nothing changes

Expected Results

The error message should not be shown since the issue is added to the Sprint.

Actual Results

An error message related to the Schedule Issue permission is shown even though the issue is added to the Active Sprint.

Workaround

It's possible to build an Automation rule to, whenever Sprint field is updated, if the issue is on the specific status, clear the Sprint field. However, this action is done silently and the user may not notice the issue was not added to the Sprint since no error message will be shown.