Add custom check while creating a new Project in JIRA CLOUD

[javed.faruquee]

Hi

We are migrating from server to an existing cloud option, as miggration can take few months time it could be possible that there could be lot of projects which would get created having same Project Keys on Cloud which we have on our server instance,

What we want to do it restrict creation of projects keys on cloud with same keys as ours in order to avoid unwanted work at our end.

We were thinking if there is a way we can use some automation/script to read a LIST/CSV  having all our project code and during creation of new project on cloud if it finds the project key which already exists on LIST/CSV (which we already have on server) it should not go ahead and create the project on Cloud and gives user a message to choose other project key since project key entered is resereved.

Can something like this is possible on Cloud?? Please share inputs.

Also, if something similar can be done for SPACES on Clonfluence Cloud?

Thanks

Javed

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

I'm afraid there's no function to limit the use of project keys in Cloud (or Server for that matter).  Other than "it's been used in this system already"

You have to trust your couple of admins to check your current list of keys before they create a new Company-managed-projects.

I'd suggest limiting the permission to create team-managed projects to the same admins, at least until you have completed your migration.

There is another option, but it might not fit with your migration method - create the projects with the reserved keys, but no issues.  Then import the issues when you migrate the teams using the projects to Cloud.  The empty projects will sit there waiting for their users to migrate, but blocking new duplicate-keyed projects.

[Walter Buggenhout]

Hi @javed.faruquee and welcome to the Community!

While that is great thinking, that is unfortunately not possible. The only way I would theoretically see you being able to block project keys from being used for new projects, would be to create them there. But since that's exactly what you want to avoid, I would strongly advise you not to do so.

Having been involved in a couple of migrations by now, I would also recommend you not to let your users go wild on your new instance in the cloud too much. Migration in itself is a pretty complex matter and a lot of uncontrolled changes leading up to it can cause you some serious headaches by the time you're about to start your production migration.

So, as a workaround, I would suggest you pull a list of project / space keys that should not be used in the cloud. And limit the permissions to create new projects on your cloud site to a very limited number of people who are involved in migration preparations and are aware of that list.

Hope this helps!