Open aarju opened 2 years ago
Pinging @elastic/fleet (Team:Fleet)
Thanks for the feedback @aarju! Some of the steps here can be skipped. Agent policies do not have to set up before going into Integrations. At the time of adding an integration, a new agent policy can be created on-the-fly.
Clicking "Add integration" from within an agent policy should be preserving the context of that agent policy so that you do not have to search for the policy in the Existing hosts drop down.
Even without these two points, I agree we have a lot of room for improvement in the nth time user experience. cc @mukeshelastic and @dborodyansky: good feedback as we look towards improving that UX.
@dborodyansky & @kpollich inline with what we discussed this morning. Can we use this issue to pursue the changes we discussed and hopefully @aarju & team can validate the changes.
Can we use the figma as definition for this?
@dborodyansky I am assuming the problems described here will be addressed by out fleet Information architecture redesign..
@mukeshelastic Yes, I believe a good amount of the noted issues will be addressed by revising the IA as we have been discussing. There are some interaction specifics to sort out, but the problem here is well defined and addressable.
@mukeshelastic @kpollich and @jen-huang : Not sure how to pursue this at the moment. Are the figma presented by Dmitry good enough for us to follow through on and perhaps get feedback from @aarju ?
If I recall, the Figma mocks would be a good place to start a discussion, but they're more geared towards brainstorming than immediate execution. It'd be good to meet and discuss Dmitry's mocks and turn them into an actionable implementation plan here. Creating a hierarchical mapping of URL structure based on the mocks would be a good first step, as that would tell us how much code will need to change around Fleet's routing.
thanks @kpollich. Do you have a link to those proposals?
Let's put this on hold until we have a design resource to handle this.
I believe this is addressed in Fleet IA #157725
@jen-huang as this is now ready from a design stand point i'm changing the status and moving it to one of our upcoming sprint.
After discussing this with @kpollich , it was decided to narrow the scope of this issue to address the most needed changes proposed by this long standing issue to better the navigation for integrations. All discussions below are in reference to the details of design in this Figma.
Introduce a new tab listing all the integrations. This provides a great summary of how integrations are currently deployed.
Minor changes here to make it a bit easier to navigate
Thanks Nima - I can break this down into individual tracking issues. Perfect!
When the user navigates away from Fleet to the integrations plugin, ensure they can easily get back by updating the breadcrumbs at the top of the page. Currently once they leave Fleet, they have to go to the side bar to get back. Make it a stress free navigation between Fleet-->Integrations.
Do we have specifics for what we need to build or change here?
Per @nimarezainia - right now when adding an integration from the Fleet app, we redirect the user to the integrations app and then it's not possible to click back into Fleet using the breadcrumbs. We should have better, more dynamic breadcrumbs that allow the user to retrace their steps more quickly.
@kpollich do we want to assign this to a sprint?
Updated to clarify this is being treated as a meta. The sub-issues are scheduled in sprints.
Describe the feature: When Managing Fleet a user will often transition between Agents, Agent Policies, Integration Policies, and Integration settings as part of their workflows. At this time the UX flow between these pages is disconnected and confusing. When managing Fleet the UX flow between each page should be smoother. Within our Fleet we had to set up multiple separate Agent policies for our endpoints and it took over an hour to fully configure 4 policies.
Describe a specific use case for the feature: This is the current workflow for creating a new Agent Policy and setting up integrations:
Create Agent Policy