Hi Mark, to your first question “why was this not an RFC”: the manage app experience changes are nearly exclusively admin related. The partner impact is around app installation feature only which we have replicated 1:1 in admin.atlassian.com. I therefore opted for an informative CDAC post rather than RFC - I appreciate the RFC format is the preferred format in any case and will choose RFC over a CDAC post going forward
On your point in productivity impact and context switching: we are trying to minimise the impact on productivity caused by context switching for both, admins and partners. If you believe the new experience impacts your productivity excessively I would be keen to know more about this and would be happy follow up on this with you if you are interested.
True, if you exclude every Marketplace and Solution Partner. People working for or with Marketplace and Solutions Partners will also be impacted as these people will be installing, updating and uninstalling far more apps from far more cloud sites then the typical site admin of an customer.
This is for the reason for asking why not a RFC.
I would be more then happy to connect with you on the context switching impact. Are you going to be in Barcelona by any chance? I’ll be there so we can connect there if you are. Otherwise I would love to connect via a call to discuss this.
The gist for me:
The current process:
Go to Manage Apps
Click upload
Specify the url of the app to install
Wait for it to be done
As I understand it, the new process will look like this:
Navigate to Manage Apps - you will be dropped in the Site Connected apps page, which is not aware were you came from
In case you are dropped on the ‘Installed Apps’ tab, click on ‘Settings’
Select either unlisted or private app to install
You now need to select the product to install the app on
Specify the app url
Click Install
Find your way back
The problem for me is not so much that I need to take twice the number of actions to complete the same thing. The problem for me is the context switch made in step 1, you then need to remember where you came from in step 4 and 7 to complete the task at hand.
Now if flow a automated like OAuth for example then that would really help. Not sure if you ever had to do the OAuth handshake, but you start in one place, get redirected to other places where you need to take action, and endup where you started. If a flow like this can be build for installing apps then that would take away my concerns.
Speaking of a 1:1 replication, are you able to confirm that the UPM audit log will still be populated when apps are installed through the new interface?
@markrekveld I won’t be in Barcelona unfortunately but happy to connect with you thereafter to dig deeper into this topic and options to address the concern. Thanks for taking the time to run me through this!
@JuliaDaehne I have a question regarding the already mentioned topic of the future less visible links Get started and Configure. It is important for us that users (admins) know how to start when they use our app for the first time. At the moment, when you install an app from the Marketplace, you get the successful installation message, which also contains the Get started and Configure links (if defined).
I assume that this won’t change and that only the “Manage app” link will lead to the corresponding page on admin.atlassian.com for the selected instance in future? Can you confirm this?
we are trying to minimise the impact on productivity caused by context switching for both, admins and partners.
Some admins like myself would raise here, that moving the app management to admin.atlassian.com is in fact context switching. Considering that changing the base url, open the link in another browser tab or simply leaving where you are right know (e.g. a random ticket to upgrade an app in the application where you read the ticket) is context switching.
In practice if someone get a Jira ticket to install an app on Confluence or Jira he would anyhow open another browser tab / windows. If the app must be installed in Jira it would be less context switching. If the app must be installed in Confluence it would be context switching. Putting it behind admin.atlassian.com, it would be always context switching!
After the app is installed, the agent needs to go back to his ticket and respond to the requestor that it is installed, he has to update maybe internal documentation to ensure governance, etc.
Also for reviewing and changing app default settings, etc. i’ll have to switch the context again.
Also from a change management perspective you talk about Jira or Confluence when it comes to maintenance, etc.
The only admin task where a consolidated view would makes sense is when you have to create your budget for the next year and this already exists in the billing section.
@JuliaDaehne will there be an EAP of some sort for partners to get an early look at this? I’m hopeful the admin pages for our app will still be visible to a local site admin and I think from your response to @danielwester that they will be - but honestly I’ll feel a lot better when I see that.
Hi @daviddrawio, no changes have been made. The two ‘manage app’ experiences run alongside until end of January.
I was able to unsubscribe my Draw.io app earlier and didn’t encounter any issues. Is there a particular error message customers are referencing?
Hi @SunpriyaAppfire@jeffryan you can use the Connected Apps experience already today to test upload apps and test license states. The in-product UPM experience will still be available until end of January
By Default, the system apps should not be displayed just like the old UI. It’s quite confusing and I think most of the time the admin wants to interact with the marketplace apps and not the system apps
The screen jumps when using the actions button (e.g. click on one action button at the end of the list, scroll up and click on another button => the screen will scroll back to the first button)
At first I could not find the option to enter / change the private token and license status. Only after searching this thead I found out that it’s within app settings, which is unexpected
Details of an app are hidden behind a page change that takes around 2-3 seconds (EU)
There is no clear way to go back to the list in the last state (Filter)
Many actions are missing from the list (Update, Unsubscribe etc.)
You should be able to add important columns to the List (License status, Vendor) and hide columns that you don’t need
That you run an outdated version is even less visible now
How is one supposed to install an unlisted app in Confluence? The dialog is not big enough to show all possible products (regardless of window size), and trying to use the scrollbar causes the dropdown to disappear.
Your link seems to suggest you are referring to an app’s trial status. If so, this will be visible to the site admin in Connected Apps under app details.
But I agree with you: product admins cannot access admin.atlassian.com, so the link from UPM to admin.atlassian.com to see billing related information is not helpful. This is not within the Ecosystem app management remit and should be looked at in the context of admin roles and permissions.
we don’t show all system apps in Connected Apps as we do in UPM. The vast majority of these system apps can’t be managed by admins as they are part of the product. There are however around 8-10 configurable system app that can be managed by an admin. Connected apps will show these in the app overview screen. The admin can choose to filter them out in his view if this is desired.
the screen jumping is a bug (thanks for spotting this); we are working on a fix
based on partner feedback in this post we will lift this feature out if the ‘settings’ tab and make it more discoverable. The same applies to the app action menu which we will bring more the front. Finally, some actions are applicable only to some app types and not others. We will harmonise this experience for admins
I’m not entirely clear on the last statement on outdated version: the app overview list is pre sorted so that apps that require updating are shown at the top of the list with an ‘update’ lozenge. Through a more prominent action menu mentioned in the previous point the CTA will become more evident as well. What else would you expect to see here?
