I have looked deeper into the case, and it seems even more worrying than I initially thought.
When a user decides to open app panel through quick-add “…” button, the following HTTP call goes to Jira:
It consists of app key and the “magic” number that is somehow related to plugin installation (or URL).
The problem is that when I move the plugin to different URL and then install it again in Jira, the “magic” number is changed and all content panels opened previously for all issues disappear (they must be open back).
I haven’t tested that in production yet, but if I’m right then, we won’t be able to change URL for the production instance of the app without affecting our customer severely (plugin panel will disappear for all of them, even though there is content available). It is a serious problem.
My questions are:
What is the “magic” number for? Why isn’t the plugin key enough?
Is there (planned) a property that could be accessed/altered by a plugin and tell “the content is already there”? This would allow Jira to show/hide the panel without user interaction?
Can anyone from the Atlassian Connect team shed some light on this?