The instance parameter (the equivalent of id here) is optional. A macro without it uses the default connection.
While there's a single connection, it's the default one, so nothing needs to be configured in the common case.
When there are several connections, the administration shows a "Default connection" select, right below the connections list.
The problem of breaking existing macros when a second server is added is solved by a listener on the configuration: when a second connection is added and no default has been chosen yet, the existing connection is saved as the default. So the macros without an instance parameter keep displaying the same data, and nobody has to edit them.
Renaming the default connection keeps it the default. Deleting it leaves no default (or the remaining connection, if only one is left). The administration warns about this before the deletion.
In the macro editor, the connection picker starts on "Default connection (<name>)", and inserting a macro doesn't write the parameter, so the pages keep following the default when the admin changes it later.
I'd suggest doing the same for the JIRA macro: make id optional (the url parameter still taking precedence), add a "default" property to the JIRA configuration plus a listener storing the existing server as the default when a second one is added, and use it as a fallback in DefaultJIRAServerResolver.
Note that the comment in DefaultJIRAServerResolver saying that using the single server by default "would break all Macro calls not specifying an id as soon as a second jira server definiton is added" would then need to be fixed: the listener above solves this. The error message just below it ("You must specify a JIRA server, using the "url" macro parameter or using the "id" macro parameter...") would also need to mention the default server.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.