Access to a second project but in product backlog, I'm unable to create / edit sprints

Isaac Kan_hgqnd4

Hi there, 

I'm currently working in two teams which requires me having access to two project in jira to manage the backlog. 

Unfortunately, with the second project I've been added to, I'm currently unable to create or edit sprints. 

I've checked my role and permission and my access seems to be the same as someone in my team who is able to administer the project, but the only thing missing is altering sprints.

Does it make a difference that one team is based in UK and another is in Belgium?

Any advice / suggestion would be appreciated! 

Trudy P Claspill

Hello @Isaac Kan 

Welcome to the Atlassian community.

My first question is have you confirmed that you are accessing a Scrum board rather than a Kanban board?

If you are accessing a Scrum board, the ability to manage sprints in a backlog relates to two things:

1. The filter used to create the backlog.

2. Having the Managed Sprints permission for every project that is within the scope of the board's filter.

When the board filter explicitly names the projects to include...

project in (X, Y, Z) order by RANK asc

...it is easy to find out if you have the Manage Sprints permission for each project.

If the board's filter does not explicitly limit the selected issues to specified projects then you have to have the Manage Sprint permission for all projects in the Jira instance.

For instance if the board filter selects issues based on Components:

component in (A, B, C) order by RANK asc

...then Jira will need to look at every project to see if there are issue in it that should be included. Your permission requirements are then based on every project. It doesn't matter if Components A, B, and C are actually used in only one project. From Jira's filter processing perspective, you need access to all the projects.

 

The next step to debugging your issue is to look at the filter for the board where you cannot create and edit sprints. If you share that with us we can point out if it does or does not explicitly limit the board to specified projects.