UX Request: unified launchpad experience for asset and non-asset jobs

[moleary-gsa]

What's the use case?

The non-asset job launchpad provides a persistent editing environment for run configs.
This experience is much nicer than the popup launchpad for assets because:

• I constantly need to reopen previous jobs and copy/paste the config into the popup as the launchpad is ephemeral
• My muscle memory hits escape when the autocomplete pops up but isn't needed, this closes the launchpad and I lose all my WIP config - this is immensely frustrating

Both these issues would be solved if the launchpad was the same as the one used for non-asset jobs.

Also I believe this would solve the following issue: #14567

Ideas of implementation

Use the exact same approach as with the non-asset jobs i.e. The <<host>>/<<code location>>/pipeline_or_job/<job name>/playground/ link would bring you to the persistent launchpad for a job as well as that view being able when clicking on a job:

This is specifically in relation to jobs, I don't need this for individual asset materializations but maybe that would be desirable.

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.