-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing actions to details pages #2261
Comments
@AlanGreene Happy New Year 🎉 |
Thanks for your interest in this issue @taechonkim, however the design work for this has just started. It will likely be at least a few weeks before we have details to share and work can start on implementing the changes. I'll share more information as soon as it's available. |
@AlanGreene Hi, I wonder about the progress of the design work. If the work is done, I want to contribute this issue. |
It's in progress. We'll share details here / issue #2306 as soon as it's ready to implement. There's a lot to consider so it may take a while but we'll keep the issues updated with any progress. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
This is still something we want to do, freezing it so it doesn't get auto-closed. |
Closing as the PipelineRun, TaskRun, and Run (Custom Task) pages now support the same set of actions as the overflow menus on their respective list pages. |
There are some actions available on the PipelineRuns / TaskRuns list pages that are not available on the details pages for a single resource of those types, e.g. delete.
Delete is conspicuously missing from this set of actions, and would be very useful so that users don't have to navigate back to the list, find the corresponding row, and click the delete action there.
Similarly once #2256 is delivered it would be nice to have access to the create action too.
Any actions available on a resource on the list page should also be available from the details page.
This will require some design work as we're also considering some changes to the existing TaskRun / PipelineRun details page structure.
The text was updated successfully, but these errors were encountered: