Problem / Motivation:

Rules' Queue API integration is powerful, yet very often, users do not realize that they can natively queue rule executions. This is because, conceptually, the plugin's functionality is tied directly to scheduling queued jobs, instead of using queues in general. The UX is otherwise good for both tasks; additionally, there are proposed issues for other specific improvements.

Proposed Solution

1. Rename Rules Scheduler to one of these:

  • Rules Queue Scheduler
  • Rules Job Scheduler

2. Separately, continue work on other Scheduler tasks tagged UX.

Comments

mitchell’s picture

mitchell commented

Marked #596552: Improve usability of Rules' Queue API integration as a duplicate.

tr’s picture

tr commented
Issue summary: View changes
Status: Active » Closed (won't fix)

This issue is vague - I don't know what to do with it because there are no concrete proposals other than "improve" it.

At this point in the D7 lifecycle, we're not going to change the name of the Rules Scheduler. I will consider this for D8 WHEN Rules Scheduler gets ported and IF Rules Scheduler supports a broader notion of using the queue API.

If you have specific suggestions or tasks to be performed to make the Rules scheduler more usable and/or more functional, please make the specific suggestions in separate issues.