Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Project permission [MANAGE_SPRINTS_PERMISSION] does not exist


I'm trying to migrate our Jira Server to the cloud, but the migration fails with this error message:

Project permission [MANAGE_SPRINTS_PERMISSION] does not exist

Any Ideas?



1 answer

1 accepted

1 vote
Answer accepted

Hey @Markus Pfeifer ,

I haven't had the error myself but this seems to be a plausible explanation :)


Based on that, did this happen during your first migration or is this an x'th attempt?

I found that post before, but it seems to me, that it's not exactly the same. The problem I have is a Project specific permission. I don't get it exactly - the Manage Sprints permission seems to be included by default. I don't need it as we are only 3 agents, but I'm not sure how to remove it and if it is required!?

Dirk Ronsmans Community Leader Aug 02, 2021

Hmm, you mention agents so that to me says JSM.

i'm indeed curious if you have Jira Software on premise and not in Cloud which might be messing as that permissions makes no sense in JSM?

On my JSM only cloud environment I don't have that permissions but on my JSM+JSW one I do.. so I wonder if that's messing it up.

(just brainstorming here myself for this one)

Yes, that's interesting. So we are talking about JSM on-premises, no JSW. I removed the manage sprints permission from the default scheme an the migration is currently running. I see some errors, but will wait until it is done and will then double-check, what happened and report here, if it worked or not.

Thanks for your help!

Like Dirk Ronsmans likes this
Dirk Ronsmans Community Leader Aug 02, 2021

Let us know what happens, I'm curious about this one!

I wonder if maybe JSW was installed at one point which added the permission at that time and is now then giving you issues.

Good luck!

Ok, so it looks like everything has been migrated except the boards, which I don't really need. 😀

Like Dirk Ronsmans likes this
Dirk Ronsmans Community Leader Aug 02, 2021


Like Markus Pfeifer likes this

@Markus Pfeifer @Dirk Ronsmans 

Hope you are doing well.

Kindly let me know how your resolved this issue. Currently I'm migrating Jira service desk projects getting this issue.

I believe manage sprints permission is only for Jira software projects.




Suggest an answer

Log in or Sign up to answer

Atlassian Community Events