Close Sprint Permissions issue after changing SCRUM Board Saved Filter

Nik Blanchet

After restricting some of the administration permissions on our JIRA projects, one of the Project Leads became unable to complete his Sprints. The error message was, "To update this sprint you must have the Project Administrator permissions for all of the following projects: a, b, c…"

No biggie. We expected this.

We attempted to fix this by editing his SCRUM Board's Saved Filter so it would only pull Issues from the Project he adminisers. His current Sprint and current Backlog now only show Issues from his Project.

This did not fix the issue. Same error message. ???

I suspect that the issue is PREVIOUS Sprints included Issues from the other Projects that he can no longer administer. Because those Sprints are tied to his SCRUM Board's history, he still requires adinistrative access to those formerly-included Projects.

1. Is that right?
2. Is there a workaround?

Nik Blanchet

The issue was that the CURRENT Sprint had issues from other Projects in it. They were hidden for some reason that I couldn't figure out. (Even before changing the filter.)

I figured this out using the following steps.

1. Locate the Sprint ID for the current Sprint.
2. Search for issues in the Sprint that aren't in the Project(s) administered by the Project Lead.
   

   Sprint = ### AND Project not in (AAA, BBB)

3. Go Issue by Issue and edit the Sprint field to remove the latest Sprint.

Notes

• To perform Step 3, you must have the Edit Issues permission for the Issues in question.
• Additionally, if the Issue to be edited in Step 3 is Closed, you might need to edit the relevant Workflow to allow editing.