BUG in Comments Email

%3CLINGO-SUB%20id%3D%22lingo-sub-259220%22%20slang%3D%22en-US%22%3EBUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-259220%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20found%20that%20after%20a%20Planner%20Task%20has%20been%20created.%20If%20you%20change%20the%20Title%20of%20the%20Task%2C%20any%20subsequent%20emails%20that%20are%20sent%20when%20someone%20makes%20a%20comment%20will%20contain%20the%20original%20Title%20and%20not%20the%20revised%20Title.%20This%20is%20very%20confusing%20to%20Users!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327625%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327625%22%20slang%3D%22en-US%22%3ENo%2C%20unfortunately%20not!%20I%E2%80%99ll%20look%20into%20it!%20Juan%20might%20know%20!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327620%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327620%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20do%20we%20ensure%20that%20it's%20on%20the%20list%20of%20Bugs%20to%20fix%3F%20Or%20does%20this%20dialogue%20guarantee%20that%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327616%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327616%22%20slang%3D%22en-US%22%3E%3CP%3EYup!%20I%20could%20recreate%20it%20now!%20Still%20there...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327608%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327608%22%20slang%3D%22en-US%22%3E%3CP%3EThanks!%20I%20simply%20created%20a%20task%20and%20initially%20named%20it%20%22DEVELOPMENT%20TEST%22%20and%20then%20added%20the%20task.%20I%20then%20added%20a%20comment%20and%26nbsp%3Bsent%20it.%20Then%20changed%20the%20name%20and%20added%20an%20additional%20comment%20and%26nbsp%3Bsent%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327604%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327604%22%20slang%3D%22en-US%22%3EAlright!%20I%20didn%E2%80%99t%20get%20this!%20I%E2%80%99ll%20try%20to%20recreate%20the%20issue%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327602%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327602%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%2C%20it's%20not%20fixed.%20Please%20see%20the%20test%20I%20just%20did.%20Note%20the%20subject%20line%20of%20the%20email%20referencing%20the%20old%20name%20of%20the%20task%20and%20the%20notation%20in%20the%20very%20same%20email%20calling%20out%20the%20new%20name.%20When%20a%20task%20owner%20is%20expecting%20a%20new%20task%20name%20and%20get's%20the%20old%20one%20in%20the%20subject%20line%20it%20creates%20confusion.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327579%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327579%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20tried%20it%20and%20the%20mail%20I%20got%20had%20the%20new%20task%20name!!%20So%20it%20seems%20to%20be%20fixed!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2F%20ADam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327574%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327574%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20this%20bug%20get%20on%20the%20bug%20fix%20list%20because%20it's%20still%20a%20problem.%20Is%20it%20possible%20to%20get%20an%20ETA%20on%20when%20it%20might%20get%20fixed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-260759%22%20slang%3D%22en-US%22%3ERe%3A%20BUG%20in%20Comments%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-260759%22%20slang%3D%22en-US%22%3EYep%2C%20a%20bug%20that%20should%20be%20fixed%3C%2FLINGO-BODY%3E
Occasional Visitor

I have found that after a Planner Task has been created. If you change the Title of the Task, any subsequent emails that are sent when someone makes a comment will contain the original Title and not the revised Title. This is very confusing to Users!

9 Replies
Yep, a bug that should be fixed

Did this bug get on the bug fix list because it's still a problem. Is it possible to get an ETA on when it might get fixed?

Just tried it and the mail I got had the new task name!! So it seems to be fixed!

 

/ ADam

Unfortunately, it's not fixed. Please see the test I just did. Note the subject line of the email referencing the old name of the task and the notation in the very same email calling out the new name. When a task owner is expecting a new task name and get's the old one in the subject line it creates confusion.

Alright! I didn’t get this! I’ll try to recreate the issue

Adam

Thanks! I simply created a task and initially named it "DEVELOPMENT TEST" and then added the task. I then added a comment and sent it. Then changed the name and added an additional comment and sent it.

Yup! I could recreate it now! Still there...

How do we ensure that it's on the list of Bugs to fix? Or does this dialogue guarantee that?

No, unfortunately not! I’ll look into it! Juan might know !

Adam