Having recently migrated all of our Connect apps to Forge, I’ve noticed a discrepancy in the Developer Console that I don’t quite understand.
For all but one of our apps, when we navigate to the Installations page, we can filter by
- version (latest, out of date)
- environment (production, staging, development)
- license (trial, active, inactive)
- edition (standard, advanced)
But for one app, we only get an environment filter. We do however get a download option:
Is this perhaps related to the number of installations (over a certain number, you can no longer filter in the console UI, and instead have to download and filter offline)?
Hi @scottohara ,
Yes, we have optimised the page for performance. For app with smaller installation count, we display the full user experience.
For those apps with larger installations, we provide limited UX and offer a downloads button for additional details.
Thanks @ChandanaMeka that explains it.
For what it’s worth, tracking adoption of new versions (particularly the first Forge version after Connect-only or Connect-on-Forge) is something I’d expect to be very common.
Having to download and query in another tool adds some unnecessary friction for what should otherwise be a fairly simple WHERE clause in a query.
I do not know what kind of technology Atlassian uses that they cannot show full UX if app has more than 1000 installs.
I am sorry but this is unaccptable.
At this point, I wouldn’t be surprised if the response from Atlassian ends up being a voicemail. Someone, somewhere, thought this was a good idea, but how they arrived at that conclusion is still a bit of a mystery to me.
Hi everyone,
This was a quick fix implemented to avoid longer load times of the page. We are working on a scalable solution for this, you could track the progress here - Jira
@ChandanaMeka is there any update on when we might expect the scalable solution for this?
I note that the linked JIRA ticket hasn’t changed since April 7 (it is currently May 30 as I write this).
It seems like an extraordinarily long time for someone to figure out how to handle larger data sets using the same filter functionality that is already present for apps with fewer than 1000 installs.
The installation page leaves a lot to be desired. In almost all cases, our only option is to download and then import into a Google sheet to filter what we need to see.
Here are a few suggestions for improvements:
- Fix the page navigation or change/fix the UI. You can only click the next or previous buttons. Hovering a random page in the navigation makes it appear clickable, but it seems disabled. If the API does not allow random page access, then the current navigation UI is badly implemented and misleading.
- Show 50 or 100 rows per page instead of just 10. Popular apps can have 1000s of installations. Finding anything with only 10 installations per page is hard to work with.
- Allow column sort. This will make it easier to find what you are looking for. Currently, in particular if the filters are gone, your only option is to click next until either your mouse gives up or you find what you are looking for.
- Allow partial search. This applies to multiple places in the developer console. The current search experience is hardly a search. You have to know and type out the full site URL; otherwise, you simply cannot search.
@ChandanaMeka Open question:
- How does the “View logs” button work in the Actions menu? I could not find any record where the button is not disabled (among the ones I checked).
The view logs enable or disable depends on if the customer has accepted to share the logs in admin hub.
@scottohara @tbinna , we are working on revamping the entire architecture. Post the changes the load time, navigation, search and filtering should work without any limitations.
The team is actively exploring the options and we will update the FRGE ticket with the estimated due date of completion.
