Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Starting sprints

Deleted user February 26, 2018

Up until now, we've been able to start our sprints without any problem.

Today, we all now get this error:

you need the manage sprints permission for all projects in the origin board to manage this sprint.

 

Does anyone know what an "Origin Board" is since I don't know, and cannot find out anything about an "Origin Board" I don't know where to go or who to ask to set the permissions for that board.

1 answer

2 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 26, 2018

It's the board where that sprint was originally created on.   Although sprints are independent of boards (meaning they can contain issues from any project and they can appear on multiple boards across multiple projects), in order to create a sprint, you have to do so from a board.   This independence can complicate this, because if you don't know which board this sprint was created on, it's possible there are other projects in play here that you might not have permissions to see.   In which case if the sprint was created in a project that you don't have permissions to view, you won't be able to correct this without a Jira administrator granting you the proper permissions in that project.

In order to do this, you need the manage sprints permission in each project on the board where this sprint was created on.

I would recommend asking the user that created this sprint, which board they used to create it.   Ultimately, that will likely be the best course of action to figure out that you are using the correct board.

Once you have the correct board:  From there edit the board settings and see what the JQL filter in use here is.   Depending on which projects this board is pulling issues in from will determine which projects you need to check you permissions in.   It's likely this is pulling issues from multiple projects.  If your JQL filter in use on this board does not have a 'project=' or 'project in' statement, then its safe to presume that it's possible Jira is gathering issues from potentially every project in this Jira instance.  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events