User with Manage Sprint permission unable to close sprint

Summary

In Jira Cloud, users many encounter an issue where they are unable to manage sprints despite having the "Manage Sprint" and "Browse Project" Permissions. This guide explains the cause of the problem and provides a solution to resolve it.

Cause

The root of the issue lies in the board filter configuration. When the board filter does not explicitly include the project name, Jira attempts to evaluate all issues across all projects in the instance. If the user lacks the "Manage Sprint" permission in any of these projects, an error occurs, preventing sprint management. Checking the Board filter a warning is shown as in the screenshot below.


Solution

To resolve this issue, users need to ensure their board filter is correctly configured to include the specific project. Follow these steps to update the board filter:

Navigate to the Board Filter:   

   - Open the relevant board in Jira.
   - Click on the "..." (more options) button in the upper right corner.
   - Select "Configure Board" from the dropdown menu.

Edit the Filter Query:   

   - Scroll down to the "Filter" section on the configuration page.
   - Click on "Edit Filter Query" to modify the JQL. This will open in a new tab.

Include the Project in the Filter:
   - Ensure the JQL query explicitly mentions the project name. For example, use project = "YourProjectName".

Save the Changes:
   - After updating the filter query to include the project, save your changes by clicking on Save filter next to the JQL query search box.

By ensuring that the board filter is correctly scoped to the relevant project, you can prevent Jira from attempting to access issues outside your permission scope, thereby avoiding errors related to sprint management.


Last modified on Dec 19, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.