Feature Request: Mass Edit, Mass Archive and Mass Delete for Services, Hardware and Users
Summary
It would be very helpful to have bulk actions for Services, Hardware, and Users, including:
- Mass edit
- Mass archive
- Mass delete
This would make administration significantly faster and reduce repetitive manual work.
Problem
Currently, managing larger numbers of services, hardware items, or users requires editing, archiving, or deleting entries one by one. This becomes time-consuming and error-prone, especially in environments with many assets or frequent organizational changes.
Examples:
- Archiving multiple outdated hardware entries
- Deleting several obsolete services
- Updating attributes for many users at once
- Cleaning up test or duplicate records
- Applying the same change to a group of selected items
Proposed Solution
Add bulk selection and bulk action functionality to the list views for:
After selecting multiple entries, administrators should be able to perform actions such as:
Mass Edit
Allow changing selected fields for multiple items at once, for example:
- Status
- Category
- Assigned user
- Location
- Department
- Tags
- Notes
- Custom fields, if available
Only fields selected by the administrator should be changed. All other fields should remain unchanged.
Mass Archive
Allow selected services, hardware items, or users to be archived in one action.
Before archiving, a confirmation dialog should show:
- Number of selected items
- Type of items selected
- Warning that the action affects multiple records
Mass Delete
Allow selected services, hardware items, or users to be deleted in one action.
Because deletion can be destructive, this should include a strong confirmation step, for example:
- Display the number of selected items
- Require confirmation before deletion
- Optionally require typing
DELETE
- Respect existing permission rules
- Prevent deletion if records are still linked to required dependencies
Permissions
Bulk actions should follow the existing permission system.
Possible permission handling:
- Users who can edit a single item can mass edit selected items
- Users who can archive a single item can mass archive selected items
- Users who can delete a single item can mass delete selected items
- If some selected items cannot be modified due to permissions, they should be skipped or reported clearly
Expected Benefits
This feature would:
- Save time for administrators
- Improve usability for larger installations
- Reduce repetitive manual actions
- Lower the risk of inconsistent data
- Make cleanup and maintenance workflows easier
Additional Notes
It would be useful if the result of a bulk action shows a short summary, for example:
- Successfully updated: 25
- Skipped due to permissions: 2
- Failed due to dependencies: 1
This would help administrators understand what happened after the action was completed.
Feature Request: Mass Edit, Mass Archive and Mass Delete for Services, Hardware and Users
Summary
It would be very helpful to have bulk actions for Services, Hardware, and Users, including:
This would make administration significantly faster and reduce repetitive manual work.
Problem
Currently, managing larger numbers of services, hardware items, or users requires editing, archiving, or deleting entries one by one. This becomes time-consuming and error-prone, especially in environments with many assets or frequent organizational changes.
Examples:
Proposed Solution
Add bulk selection and bulk action functionality to the list views for:
After selecting multiple entries, administrators should be able to perform actions such as:
Mass Edit
Allow changing selected fields for multiple items at once, for example:
Only fields selected by the administrator should be changed. All other fields should remain unchanged.
Mass Archive
Allow selected services, hardware items, or users to be archived in one action.
Before archiving, a confirmation dialog should show:
Mass Delete
Allow selected services, hardware items, or users to be deleted in one action.
Because deletion can be destructive, this should include a strong confirmation step, for example:
DELETEPermissions
Bulk actions should follow the existing permission system.
Possible permission handling:
Expected Benefits
This feature would:
Additional Notes
It would be useful if the result of a bulk action shows a short summary, for example:
This would help administrators understand what happened after the action was completed.