[SOLVED] Unable to Start/Close Sprint - needs admin role from multiple projects

Has anyone seen this weird behavior where there is an error saying "To update this sprint you must have Project Administrator permissions for all of the following projects: project A, project B"?

However, looking at the board's configuration of filter, it should only need admin to project A - it doesn't have any issues in project B.

Error happens in two different cases

1. When a user is trying to start a sprint

2. When a user is trying to close a sprint

Versions:

JIRA 6.2.2

JIRA Agile/Greenhopper: 6.3.12

7 answers

1 accepted

Accepted Answer
1 vote

David,

please could you try to create an Agile board for the existing project A and verify that it works fine?

Regards,

Fabio

I was able to create a new Agile board for projectA and it's fine.

Ok, maybe it's time to open a ticket to support.

Atlassian support indicates that there were projectB issues in the board at sometime or another

To "close" a question, mark the best answer correct with the tick mark to the left of the answer.

1 vote

Hello David,

even if there're no issue related to Project B, because your Board is cross project, you need to be project administrator in both project to start/close a sprint.

Please, take a look here https://confluence.atlassian.com/pages/viewpage.action?pageId=298978639

Hope this helps,

Fabio

Are you sure that the board do not contain any issue/task/sub-task associated to project B? Is there any issue you moved from project B to project A?

i'm pretty sure the Agile board filter does not have any issues from project B. The filter is targeted only to project A. I looked at the filter and it doesn't have any project B issues.

0 votes

Hello David,

please could you share your dashboard filter?

Regards,

Fabio

project = projectA AND issuetype in (Bug, Task, "User Story", Sub-task) AND status in (Open, "In Progress", Reopened, "Resolved - Needs Verification", Closed, "Dev - In Progress", "QA - In Progress") ORDER BY Rank ASC

Disclaimer: I didn't create this filter, some scrum team did :P

I didn't many folks emailing me when we were in JIRA 5.2.2, however after the upgrade there have been a few. One had a simple filter "project = projectA ORDER BY Rank ASC". Both had the common issue where they needed to be admin in projectB. (Both cases projectB is our Ops project)

Versions:

JIRA 6.2.2

JIRA Agile/Greenhopper: 6.3.12

We just encountered this issue and it seems to be caused by two different projects having the same sprint name. Got to that by using this piece of support from knowledge base:

  1. Go to Issues > Search for issues
  2. Enter JQL to find issues in your sprint from other projects.
    • For example, if your project key is "ASDF" and your sprint is "ASDF Alpha" use this JQL: A Sprint = "ASDF Alpha" and Project != ASDF
  3. Execute the search and examine the results.

We got that the same sprint (by ID) is used between two projects. It looks a person from another project assigned some tickets to our sprint by modifying Sprint field in tickets. We had to revert those changes back.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,945 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you