Description

Users are getting 'Something's gone wrong' error while deleting sprints.

Steps to Reproduce

1. Login to the instance and navigate to the project -> Backlog
2. Try deleting the sprint.
3. It errors out stating 'Something's gone wrong'
4. Upon further investigating in the database by support team, there were Jira issues in the archived state.

Expected Results

While deleting the sprint, it should generate error with complete information to give the users and admin an idea what the problem is.

Actual Results

The below error is thrown

Things to Consider{}

• UX is not intuitive, making people resort to using DevTools to understand what even the issue is

• JQL archived = "true" silently returns 0 issues even when archived issues
  exist (verified: 8 archived issues, 0 surfaced via JQL)

• This makes the "There are archived issues associated with the sprint"
  deletion error practically undebuggable for end users, who have no UI
  surface that reveals which issue is blocking

• The fix would be either: (a) make JQL archived reliable, or (b) include the
  offending issue keys in the deletion error response