Jira board that references no project, user unable to start/stop sprints

[David Whitlock]

I am a JIra Admin a jira board was configured with a filter similar to this:

assignee in (user1, user 2, user3) order by rank

This board will pull in issues from many different projects

Because this filter does not reference a project, it seems that a Scrum Master can not start and stop sprints in this board, I seem to be the only person that can do so. Is there a way to assign permissions to a scrum master to handle this board

[Morgan DUBUISSON · Accepted solution]

Hello,

The issue you're encountering is expected behavior due to the way Jira handles permissions across multiple projects. Since your board's filter pulls issues from various projects without specifying one, the Scrum Master cannot start or stop sprints because they might not have the Manage Sprints permission for all the projects referenced by the board's filter. Jira requires this permission for every project involved in the board's scope in order to manage sprints.

To resolve this, there are a few options:

1. Ensure the Scrum Master has the "Manage Sprints" permission across all the projects that are part of the board's filter. This will allow them to start and stop sprints.
2. Modify the board filter to limit it to projects where the Scrum Master has the necessary permissions.

I hope this helps clarify the situation! Let me know if you need further assistance.

Best regards.

[Trudy Claspill]

Adding to this...

The results of the filter may  end up with issues from only a small number of projects where the Scrum Master has the necessary permissions, but Jira is not evaluating permissions based on the projects from which results are obtained.

When projects are not explicitly declared in the filter Jira will require the user have the necessary permissions in absolutely all projects in Jira.

If you know that the Assignees will only be used in a few projects then you can add those projects to the filter and ensure that the scrum master has the necessary permissions in that smaller set of projects.

[Nicketa]

Make sure, the scrum master has been added to all those projects with browse issue permission as well as manage issue permission.

if scrum master is not in all projects, they’ll not be able to see all issues assigned to those people. They can only see issues in the project where they have permission.

But the question is, why anyone would have this kind of filter for boards (scrum or kanban). If idea is to track all issues assigned to particular person or group, they can use Dashboards with this filter. Even they can use quick filters in a board based on assignee. For Scrum, they can use more relevant filter related to project only.