Change project key for source code integration?

[Kevin Davis]

We have a next-gen project that had issues migrated to it from another project. When that migration was complete, we deleted the old board. We changed the project key, and the issues in the board use that key correctly. However for source code integration we must tag our commits with the old project key. Can this be changed?

I assume this is because of the way the API handles project key changes, namely the API seems to ignore them:

> REST API calls will still work with old project key — REST calls that specify an issue key will work with the old issue key after the project key has changed.

https://confluence.atlassian.com/adminjiraserver086/editing-a-project-key-990553076.html

Does this mean we have no recourse to change the source code key to match the new product key?