Not enough technical evaluation has done (could not take enough time to do), but no heavy pre/post works are listed, it seems system technically this change should work well and smooth.

https://confluence.atlassian.com/adminjiraserver071/editing-a-project-key-802592377.html
https://answers.atlassian.com/questions/200230/

Project name/key changed and INSTRM-1, INSTRM-2 has marked as WONTFIX.

Sorry, but I really don't like putting camera detector and electronic problems in with general software development. I think that detector&readout problems merit more than component tags or labels, partly because they will be treated quite differently, and will be handled by different people. Also, some will never be fixed but should be tracked.

Also, some H4 detector issues will not be covered by ITAR, and so can be kept with CCD issues.

I guess we could simply mark CCD, ADC, FEE, FPGA, H4, ASIC, SAM issues with those component tags or labels, but I'd still vote for keeping them in a separate project.

I missed your comment cloomis.
For now, we define the same workflow, screen items, permission over all projects, and only changes are project roles (but mostly not used). So, I don't think we gain something more than having component to categorize these, with having separate project. We also may define separated sprint if we want to do for some special period like mass gathering for pre-ship review, etc.
We may have interactions between detector control tickets and other parts, by such as FITS header definition put from other parts, SpS AIT, and it may be better to be kept in the same project.

File new ticket, if you really want to propose to have.