Cloud: Is the changing the project-key in the current projects (with more than 30K tickets) safe?

Question

Hello,

We have a necessity to change the Key values (project key) for several projects, and it's very important to know that this procedure is safe enough and won't affect any data since the projects are active and a significant amount of data there (> 28K tickets in one project for now).
What should we know before to start this process? What should we be aware? Any necessary actions that need to be performed before the start?

Thanks ahead!

Hernan Montes_6rmjzn · Answer

No worries, I imagined that the external file management would be not path based, let me know if you have any issues.

Good luck!

Maksim Feshchanka · Answer

I just tested the internal links between the two test-projects and it works as expected: links changing dynamically, once the project-key is changed.

Regarding the attachments, I meant the "Cloud Files" external S3 add-in for attachments, since the original Jira cloud attachments storage has a 20GB limit. So, these links won't appear after the key re-named (had tested before), so we'll update the project key for all the files associated with every ticket on the S3 side.

I'll add more info here once any further activities are done. Looks like there are no any step-by-step instructions about this procedure.

Thank you, @Hernan Montes !

Hernan Montes_6rmjzn · Answer

Links should update automatically between projects, as for S3 buckets, I'm not sure it is needed, the way Jira handles attachments is not affected by the key change, attachment paths do not change project key, they remain as the original key, that's why you cannot use the same project key with another project, even if you have changed the key and it is not being used, but, if the connector uses simple URL requests, then yes, you will need to change it via scripts, you can do a small test in the test project to see if buckets are still able to retrieve files when project key is changed.