Update: you should create the context before the import, but anyhow it's just to make a point of the case sensitiveness.
Batch add uses case sensitive string comparison
steps to reproduce:
import strings such as "@Home clean up the kitchen"
Create a context called "home" (or make sure there's an existing one)
Expected outcome:
The task should have assigned to the context Home.
Actual outcome:
The task didn't assign any context. The name simply contains "@Home"
import strings such as "@Home clean up the kitchen"
Create a context called "home" (or make sure there's an existing one)
Expected outcome:
The task should have assigned to the context Home.
Actual outcome:
The task didn't assign any context. The name simply contains "@Home"
-
04/06/2014 18:03#1PRO
-
04/08/2014 09:41#2PRO
@zmfile01
Hi,
Do you want that the task is added the context Home and the task title should not contain "@Home" when you input "@Home clean up the kitchen"?
Best regards,
Doit.im Team -
04/09/2014 15:52#3PRO
yes that's correct.
In fact the system would already do so if "Home" is an existing context.
Note that here the key issue is case sensitivity. If the existing context is "home" instead of "Home", the context won't be assigned correctly. -
04/10/2014 01:59#4PRO
@zmfile01
Hi,
Thank you for your feedback.
Some words have different definitions when you capitalize the first letter. We will consider this issue seriously.
Best regards,
Doit.im Team