We have a large & complex web application where users currently can perform certain tasks, but they have to sit on the page and wait for them to complete. Some of these take a really long time, so we are about to add a "long running task" framework that will allow users to kick off a task, something else will process it, and they are updated later when it has completed. They don't have to sit around and wait any more.
It would be an icon & menu in a top bar. Clicking it would expand the menu to show all current things being processed, and any past ones that have completed or failed.
Right now we are struggling with what to name this feature because it needs to be obvious as to what it means, and it needs to be generic enough to contain any kind of operation that might take a while to complete.
Some examples of tasks that we will probably throw at this:
- Ordering a single service for a user
- Ordering a service for multiple users
- Changing a setting/preference for multiple users
- Importing settings for multiple users from an external source (CSV file, etc.)
Right now we have a few names in mind, none of which I'm crazy about.
- The argument for this one is that anything can be an "order", even changing settings.
- I don't think that most users will think about things in these terms like "I've placed an order to reset Bob's password"
- We don't love this one, and the name doesn't seem to have a lot of meaning behind it. I don't think people will grasp what this means all the time.
- Long-Running Tasks
- This name feels overly technical to me
Based on this thread and some discussiong we had, I've changed the name to "Tasks" for now. Below is a screen recording of a semi-functional mockup of the UI and how this might work.