Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,347 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@dee077 ci sta già lavorando.

Dal 6/5/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement gsoc

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.

Lingua principale
Python
Stelle
779
Fork
328
Merge medio
2g 19h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openwisp/openwisp-controller

Tutte le issue di openwisp/openwisp-controller

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.