Ticket numbering scheme should be changed to support multiple Jiras in an organization

Today the tickets in Jira are named xxx-yyy.

If you run multiple Jiras for scalability or geography, this limits your ability to distinguish multiple Jiras. The workaround is to select xxx's which are globally unique to an organization, but this would not help if a company acquired another company with Jira.

Instead, the system should let you identify a server with a code, maybe two extra characters, and then tickets would be referenced as
AA-XXX-YYY.

Perhaps another scheme could be dreamed up to make it even easier since it would be nice not to type extra characters.

Goals:
1. From a ticket, I need to know which server it came from.
-For example, fisheye would have to know from the check-in comment.
-My other applications need to know so I can visualize the right Jira ticket and URL based on the ticket

Today's workaround:
1. Require administrator to have distinct three letter codes
2. Never acquire a company with Jira, as the three letter codes cannot be changed (in any case, all the check-in comments from the past would be wrong.)
3. Maintain a table which maps the three letter codes to the respective URL for the correct Jira. That way I can lookup the URL.
4. Don't put a lot of tickets in Jira, and live with one server

This ticket clearly requires considerable discussion.