That's just another set of words meaning the same thing. You need to explain what you think it is. Let me put it another way. You have a JIRA installation. Please look at it and point at the physical string on a screen that shows this "unique installation identifier" that you want to extract.
That's what I'm trying to get at - there's loads of things it could be, and "instance id" is meaningless. Base url is a good way to do it (until you're on data-centre, where it might not be, because you'll have many installs on one url). Or there's the SEN. Or the Server ID (which you can change). Or. Or. Or...
For the JIRA instance id I would use its base URL: https://<company>.atlassian.net
For the project id, I would use the pid number. I guess there are more elegant (REST API) ways of getting them, but you can look at each project's id by hovering your mouse over their 'edit' option in administrator's projects view: https://<company>.atlassian.net/secure/project/ViewProjects.jspa
and looking at the status bar at the bottom of your browser's window. There you will see a URL which includes 'pid=<number>', and that's the number you might want to use.
The problem here is that we don't know what "instance id" means to the questioner. Also, the base-url might not work for Data Center (one base url, several instances) Although you're spot on with the project ID - I'd always use the project ID as it's immutable and unique.
If you are writing an Atlassian connect addon then you should use the 'clientKey' that the /installed lifecycle event gives you: https://developer.atlassian.com/static/connect/docs/latest/modules/lifecycle.html That is a unique identifier for Cloud for every instance.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot