Major Data-Destructive Bug
(closed account) says:
With, for example, the tags field, is a variable for what's already there. So if you have it as ", newtag", you are leaving what's already there intact and adding the "newtag" tag to each of those, even if they differ.
If you go to the task field, however, and add a string "newstring" to the task name in there, it does not add that string to each task -- it literally replaces each and every task with the phrase " newstring" -- with "" being reproduced literally as the word "multiple" not as the new variable.
Now, mind you, the functionality to have the task name behave like the tags field would be ideal. But the user should be prevented from destroying his work like that. (Fortunately, I was able to undo it -- even though, oddly enough, the "undo" notice did not show up.)
If you go to the task field, however, and add a string "newstring" to the task name in there, it does not add that string to each task -- it literally replaces each and every task with the phrase " newstring" -- with "" being reproduced literally as the word "multiple" not as the new variable.
Now, mind you, the functionality to have the task name behave like the tags field would be ideal. But the user should be prevented from destroying his work like that. (Fortunately, I was able to undo it -- even though, oddly enough, the "undo" notice did not show up.)
emily (Remember The Milk) says:
Multi-editing tags is a special case (described here), to make it possible to add to the list of tag attributes.
Multi-edit for any other property will literally take whatever is entered in the field and replace that property for all selected tasks. (Multi-editing can be pretty destructive, which is why it's a separate mode rather than the default.)
To lessen the confusion with multi-edit (particulary with the way that multi-edit and tags works), we'll see if we can prevent users from renaming tasks to include a literal <Multiple> in their name (as that never makes sense).
Thanks for your feedback on this!
Multi-edit for any other property will literally take whatever is entered in the field and replace that property for all selected tasks. (Multi-editing can be pretty destructive, which is why it's a separate mode rather than the default.)
To lessen the confusion with multi-edit (particulary with the way that multi-edit and tags works), we'll see if we can prevent users from renaming tasks to include a literal <Multiple> in their name (as that never makes sense).
Thanks for your feedback on this!
(closed account) says:
Thanks for the response. I then suppose what you probably may want to make clear to the user is that the behavior of the in the tag field is unique to that field, and carries over in no other field -- not just tasks but anywhere else.