How to run a sprint on issues from several projects?

[Kathrine Lønning]

Hi, 

We are struggling with a case where a team normally working on 2 projects (combined into 1 board with a filter), but we now also need this team to pick up some issues from other selected projects, and add the issues into their board.

We need to specify the exact issue we want to include from other projects in stead of everything in other projects. 
Eg.  project in ("X", "Y") OR parentEpic = Z-123 OR parentEpic = ZZ-123 ORDER BY Rank ASC

When we try to do this, the person who administrate the sprints has no longer access to create, start and stop spints. I have given this person project admin access to the selected projects where these issues belongs to, but seems that I have to give this person admin access to ALL projects in our Jira instans?? 

Do anyone of you any experience from this?
Is there a simple solution for how to build a filter, not running through all projects?

(I have already given the person a general role with Manage Sprint access.. not working. And when testing with the "permission tester" in Jira, it gives "green light" on manage sprint on the zz-issues)

This case will occure more going forward, since teams will be handling issues more across projects to help out where needed, so I would love to find a good solution to this asap.. :) 

Thanks in advance! 

[Karan Sachdev]

Hey Kathrine,

Usually, if a user is unable to create, start or complete sprints on a board that includes multiple projects, it's a permission issue. The user must have the permissions to manage sprints on all the projects included in the filter.

The below permissions are required:

• Manage Sprints
• Edit Issues
• Schedule Issues

To ensure that the required user(s) are granted permissions to the required projects only, you may have to review your permission scheme. Does it apply to all the projects?

If yes, grant the permissions to project roles instead of groups, and add these users to the project roles in the required projects only.

Additionally, the JQL query might need correction. To include child issues of the epic Z-123, you need to add "Parent = Z-123" in your JQL. If you want to include the epic itself, include "issuekey = Z-123".

You may tweak the expression as required and it should be sorted.

I hope this helps!

Thanks,

Karan