Tasks - Focused Notebook Experience

Product Brief: https://docs.google.com/document/d/1-E4b4NXMWyPBNpax4UQe2QHekGBRIpAboAzVyynWeN4/edit#

**EPIC Description**

Today, the ability within the UI to create a task from the task menu is very rudimentary. You are given a blank screen with a text box to start writing a script. A better user experience was created via Notebooks, which gives some query builder assistance and flux assistance to the user as they build their script. But there is still a desire to be able to go in and view task run/history/logs from the main menu, without having to go into Notebooks. This has made creating tasks in notebooks without it causing user confusion a challenge. This EPIC is to allow that notebook experience to be used/perceived at the task menu level, with all non-applicable notebook panels hidden/removed and the notebook name masked/hidden to the user (only the task named retained). To the user, it will look like an enhanced create task/task menu, but they won't have the confusion of moving off of the tasks UI and onto the Notebooks UI. They won't have to have a notebooks name + a system defined task name, they will just have a task name that they will save.

**Business Justification**

Making tasks easy to create and generate is one of the easiest methods that can be used to gain additional usage and consequently revenue. However, our interface for creating tasks doesn't make it very easy for the user to create them and for the new user evaluating the product, gives a poor first impression. General feedback on creating tasks in the cloud UI shows dramatic room for improvement. Improvement was arguably made via the task creation in Notebooks, however it introduced great confusion and just the internal feedback received was that users didn't know where they should go find their tasks/edit their tasks, etc. We need to continue to iterate on this to make it more attractive to new users and to make it easier to generate new recurring tasks that will gain more usage.

**Current Problems to Solve**

Largely blank screen with a "1." is harsh user experience for the brand new user and is inconsistent with other areas of the UI where we give some visual assistance to them in building a flux script (query builder, flux function list, doc links, etc.)
Using Notebooks has aided the original problem, but has introduced confusion around where to edit, see run history, and how to find tasks that has created friction even within the internal organization. Maintaining two names and correlating them to each other is another big obstacle.

**Key Acceptance Criteria**

- When a user chooses to create a task from the task menu, it doesn't appear to them that they have automatically switched to a different menu option(notebooks) in the UI (even though they may be using notebook code); to the user, they still appear to be in "tasks" and not "notebooks".
- The user only manages one name (not a notebook name, and a user or system defined task name). That doesn't mean there can't be a hidden notebook name behind the scenes that invisibly maps to the task name. But if so, that hidden name shouldn't be visible from the notebooks list.
- The user experience for creating the task is mainly the user experience of creating a task in notebooks (versus the current user experience in tasks)
- Any task previously created in tasks, will be editable via this interface.
- The user , by default doesn't see all the "+" options that are normally seen in Notebooks and by-default only sees a query panel and a task panel. Table, Graph, and Alert , etc. panels are there unless explicitly added by the user.
- Tasks created in the UI are available via the API as well