Summary | bulk message processing |
Queue | IMP |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | viktor (at) szepe (dot) net |
Created | 11/11/2014 (3866 days ago) |
Due | |
Updated | 11/13/2014 (3864 days ago) |
Assigned | |
Resolved | 11/13/2014 (3864 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
timeout (or get faster backend components). Setting "action" limits
is an absolutely terrible UX.
There's a chance that certain actions (i.e. login tasks) may be moved
to a queue/deferred action handler in the future, but that isn't
relevant here.
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ bulk message processing
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
memory limit.
I suggest to add a new filter to Search and Filters: "Result limit"
It would limit the number of results to a given number.
Thank you!