Migration error

[System Administrator]

I have a single project which is failing the migration check.  The error is:

ERROR SYS project-export Permission holder 'reportercreate' is not supported for Permission Key 'Edit issues' on Permission Scheme 'Systems' . [JCMA 113]

Can anyone help me understand what this is trying to tell me?

[Rune Rasmussen]

It seems to be telling you that in your Permission Scheme called "Systems" the permission of "Edit issues" is given to something called "reportercreate" which is not compatible with cloud.

I have no idea what "reportercreate" is though, but I would look at that specific permission scheme and that permission.

[System Administrator]

That is apparent from the message, my problem is that I can't make sense of where I go to check on it.

[G.A.]

Maybe this can help - [JRASERVER-13301] Error when using reportercreate if Reporter has the Create Issue permission in a permission scheme - Create and track feature requests for Atlassian products.

might be related to special configurations in the installation XML files - atlassian-jira/WEB-INF/classes/permission-types.xml

[System Administrator]

Now that I recognise!  Thank you.  Strangely that is applied to all the permissions schemes and none of the rest threw errors in migration.  Anyway, I've got past it now and since the project in question is really only there for archiving (I found Jira quite unsuitable for the IT helpdesk job it was trying to do) it shouldn't matter anyway.

[System Administrator]

https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/

I followed this.  I have never really understood the convoluted way these things work but in the end I found under Settings, Issues, Permission Schemes there was a Scheme called Systems.  This had several elements with permissions assigned to "Reporter (show only projects with create permission)" which sounded very much like the item causing the errors.  Once I removed the permissions the error messages went away.

It's odd, given that the same permissions appeared in other schemes without causing problems but this worked so I'll take it.