This seems to imply that at the point in time when a project key is released, all existing references will stop working (e.g. in stored JQL queries, issue keys?).
Yes, all statically referenced keys will be affected and will need to be updated.
Would that also affect the normal REST APIs for example?
Indeed it would, but for most of the APIs, there is an option to use ProjectId rather than ProjectKey, in those cases, calls using ProjectId will not be affected - which is what we recommend using.
A very nice feature indeed! @Carol Low Just wondering: which admin level is this connected to - permission wise? Is this only changeable by Jira Admins or can a Project Admin also remove the old project key?
This is wonderful!! Thank you Atlassian for having this as an option for both team and company managed products. ((happy dance))
I saw the questions about JPD and looking forward to that! We are still in discovery of using JPD in other Atlassian products and have gone through using various project keys /renaming. Looking forward for JPD next! Is there a feature request open link to follow?
Hi @Carol Low, just wanted to follow up on the status of reusing project keys in JSM. Is there a ticket for this that we can watch so we don't have to bug you about it? 😁
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
@Anne Saunders Hey! Thanks for the reply. For anyone searching, while you're correct that the option will show up, it look like the feature is still disabled for JSM.
That's correct, this functionality is not available for JSM projects. Support for releasing keys for JSM is quite a bit more complicated to implement and is not currently prioritised.
35 comments