Actions
Feature #5283
closed
Design bulk actions architecture.
Description
During the course of re-designing tupane, the bulk actions feature has revealed the need for a robust bulk action architecture. Actions that reach out to physical systems, or backend services may experience some time delay and need to be handled asynchronously with reporting to the user on status.
Need to work with Foreman to unify on a Bulk Actions mechanism, most likely utilizing mcollective
----
Imported from https://trello.com/c/5foUhFzS/117-8-design-bulk-actions-architecture_
Updated by Eric Helms over 9 years ago
- Subject changed from [8] Design bulk actions architecture. to Design bulk actions architecture.
- Status changed from New to Needs design
- translation missing: en.field_story_points set to 8.0
- Triaged set to No
Updated by Eric Helms over 9 years ago
- Status changed from Needs design to Resolved
- Triaged changed from No to Yes
Updated by Eric Helms almost 8 years ago
- translation missing: en.field_release set to 166
Actions