Issue Summary

If a user without Schedule issues permission for an issue tries to add it to a sprint, the error given is a generic "Something's gone wrong. Refresh the page and try again." instead of a warning that the user's permissions don't allow the action.

This doesn't give an admin any information to go on to identify what's going wrong, and a page refresh won't help.

From the screenshot on JSWCLOUD-5977, in December 2022 the error message specifically identify the Schedule issues permission as the reason the action failed.

Steps to Reproduce

1. View a project backlog where you have Browse projects, Edit issues and Manage sprints permissions, but not Schedule issues
2. Try to drag an issue into a sprint (from backlog or another sprint)

Expected Results

User sees an error stating that they don't have the required permission, ideally identifying "Schedule issues" specifically.

Actual Results

Error is entirely generic and suggests that there's a system or data issue, not that the user doesn't have the necessary permissions.

Workaround

N/A