Currently, when a user attempts to delete a sprint that contains issues from multiple projects, Jira requires the user to have specific permissions not just in the origin project, but in all projects where the linked issues reside.

If the user lacks any of the following permissions in a related project:

• Manage Sprints

• Edit Issues

• Schedule Issues

• Move Issues

The sprint deletion fails, and the UI displays a generic "Something's gone wrong" or "An unexpected error occurred" message. This is misleading as it implies a transient system failure rather than a permission-based restriction.

 

Current Behavior:
The UI returns a non-descriptive error. The user is left unaware that the sprint contains issues from other projects they cannot modify

 

Suggested Enhancement:

1. Descriptive Error Messaging: Instead of a generic error, the UI should explicitly state: "Cannot delete sprint because you lack [Permission Name] in project [Project Key]."

1. Visibility of Linked Issues: If a sprint appears "empty" due to issue security levels or project permissions, the warning should clarify that hidden issues are preventing the action.

1. Pre-check Validation: Perform a permission check across all issues in the sprint before attempting the deletion and highlight the specific projects causing the conflict.

 

Why this is different from JRACLOUD-93506:
While https://jira.atlassian.com/browse/JRACLOUD-93506 focuses on sprints blocked by archived issues, this request specifically addresses blocks caused by active issues in other projects where the user lacks the necessary permission set to "clean up" or move those issues during the sprint deletion process.