Add a Delete/Remove action on the Runner edit page
Release notes
We are improving the overall usability and effective of Runners by polishing micro interactions in the user interface. Previously, when managing users in the admin view, you were presented with a competing number of interactions in a table that could potentially have detrimental consequences to your application, such as deleting a runner. We want to make that experience more intuitive and less invasive. With this release, you can now delete a runner by simply navigating to the detail view of that runner. Simple, right?
Problem to solve
As a user, I want to delete a runner from the detail view page, so I can be focused on a destructive task that might have detrimental consequences to my application.
Intended users
User experience goal
The user should be able to delete a runner from the runner detail page.
Proposal
- We will remove the
delete
runner button from the admin overview and add it to the runner detail view (page). - frontend use the component:button type danger.
- In the UI, keep the destructive buttons separate, and place it in the bottom of the screen (where the save button is located).
- Because the Delete button is a destructive action that can’t be undone/has potentially detrimental consequences for the application, display a confirmation modal as a secondary step before proceeding with the deletion.
- Technical Writing to provide UI text
- The modal should display the options
cancel
anddelete
. - Clicking cancel doesn't trigger an action, the modal closes.
- Clicking delete will trigger an action to the system, deleting the runner. The page should reload and a confirmation component:alert should be displayed to the user.
- Technical Writing to provide UI text
Further details
- Currently the only way for admin to remove a runner is in the admin list.
- This is consistent with such as the Issue and Merge Request pages.
Permissions and Security
-
Add expected impact to members with no access (0) -
Add expected impact to Guest (10) members -
Add expected impact to Reporter (20) members -
Add expected impact to Developer (30) members -
Add expected impact to Maintainer (40) members -
Add expected impact to Owner (50) members
Documentation
Yes, this will require an update to the documentation. cc @sselhorn
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
Users will have a more positive and standardized experience while managing runners.
What is the type of buyer?
Is this a cross-stage feature?
No.