quick add with a location that starts with a number doesn't work as expected
Hello -
When I try to add a task with quick add like -
go shopping by today #tagname @711
It adds a task called
go shopping by @711 (with appropriate deadline and tag). Then I have to manually go and set the location and fix the task. I have added the locations properly and they show up properly in contextual help. The locations I have @Home and @Work, work as expected, but @365m does not work the same way.
Is this a known bug? and are there plans to fix it, if known?
Someone from RTM can feel free to contact me or look at my account if specific example is needed.
thx
Scott
andrewski (Remember The Milk) says:
Hi Scott,
I've added this to our list to investigate; sorry for the inconvenience.
In the meantime, as you mentioned, you may have to set the location separately from adding the task (or rename your locations not to just consist of numbers).
Hope this helps!
I've added this to our list to investigate; sorry for the inconvenience.
In the meantime, as you mentioned, you may have to set the location separately from adding the task (or rename your locations not to just consist of numbers).
Hope this helps!
stu28bu says:
I'm having a similar issue where if you specify the location before the due date then neither the location nor the due date get set.
But if you set the due date first and then the location, then they both get set.
But if you set the due date first and then the location, then they both get set.
sfaruque says:
I'm experiencing this too. Just like [drenalin], whenever I add the task that has numbers in it, the @location field adds it to the task name.
I have the same problem. I have set four different locations (none with numbers: they are ""Casa", "Fuori" , "Mamma" and "Ovunque"). Two of them are properly added with smart add ("Fuori" and "Ovunque"), while the other two are added as a part of the task name (es: taskname @Casa),
andrewski (Remember The Milk) says:
marco.alfano,
Indeed; it sounds like you're seeing a separate but similar problem.
I've added that to our list to investigate also; thanks for letting us know.
Indeed; it sounds like you're seeing a separate but similar problem.
I've added that to our list to investigate also; thanks for letting us know.