When trying to start a sprint, the users receive the error "To update this sprint you must have Project Administrator permissions for all of the following projects: X, Y." (X and Y are internal project names)
I saw this (similar) Answer received when the submitted was trying to close a sprint. My issue differs in that they are trying to start a sprint.
The 2 people receiving this error are both set as Project Managers for the Y project, and one is set as the Project Lead for the Y project.
Any ideas what could be causing that problem?
Project manager or lead means nothing unless the permissions make them a "Project Administrator".
Check the permission schemes for both projects - what is the rule granting project admin rights? Now check that against your user's group/role/etc membership
hey Nic- Thanks for that. I get your point about permissions.
Guess I should've been more specific: I'm wondering what conditions could cause this "start sprint" permission to require Project Administrator role in two projects?
Boards do not belong to projects, there's no real "agile board for project Y". It's a board which draws its issues from project Y. And, in the case you're seeing here, it draws some from X as well. Two possibilties spring to mind first 1. Check the board configuration - what does the filter for it say? Just "project Y"? (Ignore the order by clause). Or something else? 2. Have you moved issues from project Y to X?
I get the same problem, where the systems says that admin-permissions are required for project X, Y and Z, but the person has admin rights for project Z and the board is for this project. And I cannot find any "link" to the other 2 projects X and Y ????
Understood. We have moved a lot of issues from project from project A to Z, but from the projects X and Y to Z as the error messages says. Never-mind. What is astonishing, is the fact, that when a issue is moved, JIRA keeps somewhere the original project and inhibits the project admin to start the sprint. In my opinion, this should not happen. May I ask you to check with the design team in order to find out if JIRA works as designed? I do not think, that this behaviour is sense making. Thanks
I don't work for Atlassian... Anyway, yes, it keeps the project, purely as historical thing (Issue was in XXX, and called XXX-123, so someone landing on https://myjira.com/browse/XXX-123 is automatically sent to ZZZ-456 where it was moved to). But I don't think that in itself is affecting you. I suspect the problem is that XXX-123 was put in a *sprint* while it was on the board, and Agile is keeping that information. Technically, that's correct behaviour, because you committed to work on that issue and put it in the sprint. The fact you've moved it to another project doesn't remove it from the sprint. Have a look at the issue and check if it is in a sprint (even if it's closed/done etc)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG