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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Server to JWM Migration Test: Project permission [MANAGE_SPRINTS_PERMISSION] does not exist

Edited
Jonathan Smith
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 24, 2021

I am attempting to migrate a JIRA Core Server default project with no custom columns and using default permission scheme to JIRA Work Management. 

After going though all the checks, the migration runs and I get the following results:

Selections:

Migration name: Uline Collaboration to Cloud

Destination: https://xxxxxxxx.atlassian.net

Cloud Plan JWM Cloud Standard

Projects: 1 project (collaboration), 220 issues and 9MB attachments

Users and groups: Users and groups related to the selected projects

Group membership: Users and groups will be migrated separately.

 

Check – No warnings or errors

 

After migration attempt:

Status: Incomplete

Key: COLLAB

Project Data: 42% (warning)

Attachments: Done

Users and Groups: Groups 0 of 0, Users 14 of 14


ERROR

Collab.log = 2021-06-22 18:46:57.488 ERROR COLLAB project-import We couldn't import Permission Scheme 'Default Permission Scheme'. Reason: IllegalArgumentException: Project permission [MANAGE_SPRINTS_PERMISSION] does not exist. This caused 1626 other items to fail.

When I look at the project permissions in COLLAB, Manage Sprints = Administrators in the permission scheme....

Anyone have any ideas what is causing the migration issue? The project / issues / attachments is not created on Cloud after this fails.

Thanks! 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events