while experimenting with the Issue Glance I’ve got a few questions regarding its functionality. Is this something that can be fixed, or is it intended to be like this?
- Two requests per each interaction.
When clicking on a Glance header it issues a new request to the webpanel URL. While understandable, it creates an additional load on the add-on servers. The old webpanel just opened once when an issue opens, but now each user interaction with the Glance will issue a new request.
But what is even more surprising is that the Glance issues one more request when closed! If I click on the “back” arrow to close the Glance, I get another request to the webpanel URL (with nothing on the Jira side processing the response obviously).
- Loading pause.
After a Glance has opened a webpanel and up until the webpanel receives any HTML, there is nothing on a screen, just blank space. I think the old webpanels had a spinner here with “waiting for add-on” hadn’t they? We can’t show the spinner from an add-on since no HTML is rendered in a glance’s webpanel yet, and so users are left with the blank screen for come time.
- Glance status.
If I update the issue property for a Glance status, I don’t see those updates until I reload the entire issue. Glance continues to display the old status even if I open/close it.
This effectively makes statuses not-so-dynamic. When an issue is opened I can’t renew the status because the add-on will not be called until the Glance is opened. And then even when the Glance is opened and I did renew the status, I don’t see a new value on the Glance until I refresh the entire issue.
So, basically, the status is always one step behind: it gets its value when an issue is opened (i.e. from the previous interaction with the add-on), and then it won’t get a new value until the issue is closed and reopened again (i.e. all the current working session updates will not be visible until reload).
Do you have any advice on addressing those?