Untitled Notebook Management

[garylfowler]

EPIC Description

The Notebooks feature has an "Auto-Save" capability. This was built to address the common issue of users "losing" their query when they happen to navigate away from the notebooks page or when their logon times out, or even if they encounter a system error and are taken to the github issue page (which happens frequently).

The side effect, however, is that if the user has never given the Notebook a name, it takes on the default name of "Untitled Notebook". And users can start to accumulate a lot of untitled notebooks. Further exacerbating this is the fact that we don't yet have any concept of user specific notebooks vs. account available notebooks. So that means any org with multiple users will start building up lots of untitled notebooks (that all users can see) that they have to sort through.

This EPIC is for the management of Untitled Notebooks, with the following key objectives/acceptance criteria:

• Untitled Notebooks won't accumulate forever for all to see

• Untitled Notebooks won't be visible except to the author

Some possible alternatives:

1 - We change the behavior to only show Notebooks with the name "Untitled Notebook" to the owner/creator of that Notebook. Once the user gives it a name, then it can be seen by all; this would at least keep the cleanup specific to an individual instead of the whole org. This would be a temporary measure until we get to permissioning of Notebooks, hopefully at some time in the future.

AND

2 - We tag the notebook name with an additional differentiator (like a time stamp or a serial number - i.e. Untitled Notebook - 2012-03-29-22:35:00, or Untitled Notebook 1)

3 - We auto-archive Untitled Notebooks older than x number of days if it hasn't been run or accessed

OR

4 - We prompt the user when they have Untitled Notebooks older than X number of days and ask them if they want to delete them (possibly when the notebook panel is accessed). If they say no, we don't ask again for another 30 days.

There are likely other alternatives to pursue as well. Product and Engineering will collaborate on approach.

[garylfowler]

Link to feature: https://influxdata.productboard.com/feature-board/planning/features/12695781