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

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
4,465,122
Community Members
 
Community Events
176
Community Groups

Project permission [ARCHIVE_DISCOVERY_ISSUES] does not exist

Hi everyone, 

When I try to migrate cloud to cloud from free site to jira software standarn site. I getting error.

2022-12-07T06:52:06.328168Z,8a85e185-85ff-3004-9044-80444c373d34,Migration of Project failed. Reason: IllegalArgumentException: Project permission [ARCHIVE_DISCOVERY_ISSUES] does not exist. This permissionScheme isn’t present or referenced in the database. This caused 23201 other items to fail.

Pls help us on this issue. 

Thanks

AnhLv

1 answer

0 votes

That suggests you have tried out Jira Product Discovery on the free site, but not on the target site, or that the target site has not yet had the new permissions for JPD added (I seem to remember that they only started to roll out a week or so ago, so some sites may be behind).  

I would try creating a JPD project in the target site (delete it later if you have no intention of using it further), then re-try the merge.

I am sorry, I forgot to say - I don't think you have done anything wrong here, I think you might have just run into an odd case where the data in your target system is not ready to accept data from your source, because JPD has not done all of its initial setup in the target yet.  Nothing we could have predicted or avoided!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events