Community
Participate
Working Groups
When the user creates a new task and doesn't enter a task name or any other information before closing the task, they get something called "New Task" in their task list. In this case I think the task should automatically be deleted when it is closed since it contains no information. Otherwise, you could end up with multiple tasks named "New Task." Or, maybe a new task should not be saved on default (maybe not even added to the task list) until the user manually saves or submits it? Another possibility would be to have the name in the task list update as the user types, without saving; that would probably not make sense when renaming an existing task, but it might make sense when first creating one.
Can you elaborate why it is a problem that the user ends up with several tasks called New Task?
Because they are completely useless and just create clutter. To create a new task is easy enough, why would you want to have a bunch of pre-created "New Task"s? The point is that the user started to create a task and decided not to, but they still ended up with something in their task list.
I agree with Sam. I think it is not worth saving the default task created after finishing the new task wizard process. Not sure if it is (easily) possible to not save the task (and add it to the task list) if it's a plain new task and just mark it dirty. Most tools do not save an initial artifact empty but require a saving action at some point - however Mylyn has this behaviour now, so maybe it's a regression to change it?
Agreed, the current workflow is not intuitive and it's easy to end up with a bunch of "New Tasks". How about this: The editor dirty is marked dirty when new tasks are opened. The summary is empty be default. When the editor is closed without any changes a prompt is shown to delete the task, defaulting to delete. When the editor is closed and something was changed but no summary provided the user is given the option to provide one. The proposed default is generated based on the description.
That sounds great. The only problem I see is that the name of the new task in the tab would then be blank. So maybe it would be good to keep the "New Task" as the initial summary, and if the user doesn't change the summary but changes something else, they can still be prompted with a summary generated from the description.
New Gerrit change created: https://git.eclipse.org/r/82399
Gerrit change https://git.eclipse.org/r/82399 was merged to [master]. Commit: http://git.eclipse.org/c/mylyn/org.eclipse.mylyn.tasks.git/commit/?id=6691e7f132193ac291940f274344c649ac5cfc5f
The following workflow is now implemented * When a user creates a new task it is marked as new-unsaved * When opening such a task in a task editor the editor is immediately marked dirty * If the editor is saved or the task is submitted the new-unsaved flag is cleared * When the editor is closed if the new-unsaved flag is present the user is prompted to save or delete the task * If the editor is closed when the flag is missing it follows the old save prompt workflow
