Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrate server to cloud, issues missing after migration

We're running a test migration of three representative projects, from server to cloud, working to determine the scope of work prior to starting the main migration project.

The Jira server uses JMWE, cloud migration fails unless we remove this first, we anticipate a fair amount of work at cloud to replace the functionality provided by JMEW.

All three migrations were successful using the cloud migration app/tool.

Looking at the downloadable migration reports, all issues were migrated.

Two of the projects do not display any issues.

At first this appeared to be a permission issue, for example, my "Org & Site Admin" account was not a member of the User group, adding the group to my account did not resolve the issue.  Same for another "Site Admin."

I've read advice that "Site Admin" accounts cannot see or use issues, can only manage the site, other advice is to add the User group to the account to solve the problem.

This initial proof of concept and requirements gathering is using the free tier, is free tier unable to accommodate this scenario? 




1 answer

1 accepted

0 votes
Answer accepted

Hi @Tom Emerson,

What you describe seems to point very much towards permissions, if you ask me. You need browse project permission in those projects in order to see the issues, as well ass product access to Jira Software. The first is part of project permissions, the second is part of site admin settings (user management).

Check if both are ok. And also - if you are testing out migration and plan to move to a standard or premium plan later on, do test your migration against those plans instead of the free plan. Permissions configuration in the free plan is limited.

If - after checking out the browse project permission and product access - you still can't see your issues appear, reach out to migration support - they are there to help you look into the details of your migration and help you fix any issues that require intervention from the backend - if necessary.

Hope this helps! 

We agree (reviewed with our migration team this morning.)
Likely we have "interesting" permissions on those projects at Jira Server.
Next step, we plan to try to identify what these are at Server, then re-run migration.

Either way, this is migrating to the cloud, just need to identify scope and effort before forging ahead with the full migration.

Thank you!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

233 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you