openwisp / openwisp/openwisp-controller

[feature:gsoc26] Admin action to execute mass commands from the device list page

Open
#1,347 2 comments 0 reactions 1 assignee View on GitHub

@dee077 is already working on this.

Since May 6, 2026.

enhancement gsoc
Dominant language
Python
Stars
773
Forks
315
Avg merge
2d 16h
Merged PRs (30d)
14

Description

Is your feature request related to a problem? Please describe.

Administrators should also be able to select devices directly from the device list page using the existing checkbox selection in Django admin. It would be more efficient to provide an additional entry point for mass command execution directly from the device list page, allowing the selected devices to be used immediately through an admin action.

Describe the solution I would implement

I would like to add a new Django admin action on the device list page to allow administrators to initiate mass command execution directly on selected devices.

Image
  1. Add a new admin action named Mass Execute Command to the device changelist page.
  2. Administrators can select one or more devices using the existing checkbox selection in the device list page.
  3. After selecting devices and choosing Mass Execute Command from the admin actions dropdown, clicking Go should redirect the user to the mass command confirmation page.
  4. The selected devices should be pre-populated as the target devices, bypassing the device filtering step of the standard mass command workflow. From this point onward, the execution flow should follow the same workflow as the dedicated mass command admin interface.

Mentioned in #1345

Details to preserve during implementation

The redirect target after the admin action should remain open for investigation. Possible approaches include redirecting to the MassCommand admin add page, redirecting to the same confirmation page used by the dedicated workflow in #1345, or using a small intermediate view that passes the selected devices into the standard workflow.

Selected devices must be permission-filtered and multi-tenant safe before creating or confirming a MassCommand. The implementation should ensure users cannot use the admin action to execute commands on devices outside their allowed scope.

The selected devices should flow into the same confirmation and command selection workflow used by the dedicated MassCommand admin interface, unless implementation work shows a better shared path.

Automated tests should cover selected-device preservation, permission handling, multi-tenant filtering, and the redirect/confirmation flow.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.