Inconsistent saved object management experience

[tbragin]

In the course of reviewing how we work with saved objects within Kibana, I noticed that there are a fair number of inconsistencies:

New, Save and Save As

• Good news is that these experiences are consistent. For every app, you can start a new search, vis, dashboard, sheet, workspace directly from that tab. You can also save that object with a name using the "Save" menu, and save it again with a new name using the same "Save" menu, which results in "save as" behavior, where both the old and new objects are persisted. That latter point is not immediately apparent to the user, who may assume that they are actually renaming the current object.

Rename (in place)

• Discover / Visualize / Dashboard allow user to change the "title" of objects in Management >> Saved Objects editor, but modifying the object subsequently creates a new object. This is a really bad experience resulting in unexpected duplicate objects (see issue Save object workflow does not use existing ID #9012), so we can effectively consider this workflow unsupported.
• It does not seem to be possible to rename an existing object in Graph and Timelion.

Delete

• Discover / Visualize / Dashboard rely on Management >> Saved Objects editor to delete objects, individually, using explicit multi-select, using a keyword filter, or All.
• Graph only allows you to delete the workspace you are currently looking at using the "Delete" button in the top bar.
• Timelion does not have a way to delete saved sheets at all and clearly it needs one Ability to manage Timelion sheets #9055

Open questions:

• Should we introduce a more explicit "Save As" and "Rename" functionality consistently to all apps?
  • If so, is it possible do to that in a way that does not introduce a breaking change? I'm specifically concerned about the rename workflow, because right now our object ID generation logic is tied to the "title" attribute.
• Should we introduce an explicit "Delete" workflow for all apps directly from the app, rather than through Management?
  • If so, should the delete workflow available through the app itself support more than Graph does today (all, multi-select, keyword-based delete)? Or should those advanced delete options still be managed in the Saved Object view and only the single-click current object delete be available through the app?

[tbragin]

We decided to address it by improving the Save/Save As workflow in Discover, Visualize, and Dashboard: #9087

And adding a "Delete" button to Timelion, like in Graph: #9191

The object management experience between all these apps is still inconsistent, so leaving this open for the design team to explore as they rework the header navigation.

[loekvangool]

Adding an inconsistent behavior that I haven't found a report of elsewhere: If you save a Timelion sheet, the Save panel does not auto-close like in the other modules. This is in 5.3.

[elasticmachine]

Pinging @elastic/kibana-app

[stratoula]

This is not valid anymore