Why is a sprint manager not able to start or complete a sprint on a combined board using Team field?

Question

We have Shared Service teams that have their own project/board, but also have stories assigned to them from other projects throughout the organization.  They would like to be able to see ALL stories assigned to them across the organization on their one board.  To do this, we are leveraging the TEAM field to identify these shared teams.  I have a board & filter set up in a Shared Services teams' project.  It looks like this:

project = DNI OR "Team[Team]" = 63 ORDER BY Rank ASC

This should pull every story in the DNI project as well as all stories with the Team field matching, regardless of the Project.

This filter works.  The only issue we have now is that the sprint manager cannot start or complete the sprint in their project.  (In this case, it would be the DNI project.)  It makes sense that they wouldnt be able to complete the sprints from the other projects since we are pulling their stories onto our board for visibility, but why can't they manager their own sprint within their project?  As an Admin, I am able to do it for them, but Sprint Manager cannot.

Is there a way to fix this?  Some kind of creative workaround?

NOTE: I see this message at the bottom of the General board settings page:

We can't show the projects on this board, because the board's filter doesn't specify any. Your users may have trouble managing issues and sprints on this board. Try including some projects in the filter to fix this.

Thanks to anyone who will take a look!!

Fabian Lim · Accepted Answer

Hi @kellie.mingus

This is an excellent question that many members are not aware. The problem has to do with permissions on the rest of the projects. In order to manage the shared sprint board, the user needs to have access to manage the sprints on all of them.

In your filter you have "or team=xxx" which basically picks from every project in jira and provides you with hits. A quick fix would be to in include all the projects in the filter as projects in (proj1, proj2) to minimize scope and ensure that the scrum master/po has the manage sprint, browse, edit, etc. Access on those projects

I hope this helps

Bill Sheboy · Accepted Answer

Hi @kellie.mingus

I believe another way to solve the Jira project/permissions constraints may be described in how your team works:

* when a shared service team does work on behalf of other client teams, that request belongs to the shared service team...
* the shared service team probably has some form of intake, to help limit their work in progress (WIP) and to form shared expectations with clients...
* and the shared service team may have different process steps (e.g. on their board) than their community of client teams' processes...so
* why not just have the work in the shared service team project and only on their board?

Such work items could be marked (labels, components, etc.) with the client team name, and the client team(s) can view the shared service team's board when they want to know progress.

Kind regards,
Bill