Default context for a project gets first letter capitalised
This bug is present in version 1.7 as hosted on http://tra.in. It is not present in version 1.6, as hosted on http://morphexchange.com.
Details:
Details:
- If a default context is created for a project (with the intention that all next actions for that project will get the same default), the first letter of the context gets capitalised. Now if the same context has been defined separately without the first letter being capitalised, tracks treats both these contexts as different.
- Tracks is not allowing such a default context to be changed to blank. It gets reset to the originally defined, first letter capitalised context.
- If the cursor enters the field meant for defining the default context, both firefox and internet explorer start using 100% CPU. ie also gives message: "a script on this page is causing ie to run slowly..., etc.".
- I tried context "work" which gets converted to "Work"
Leave a comment
on 2010-05-18 01:49 *
By orlando.richards
I can't get it either. I have seen it in the past.
However, it is possible to create two contexts "context1" and "Context1" - from the context screen ( https://blah/contexts ). Seems pretty stable in choosing the first of the two created though ("context1" in this case).
Related - creating a context "Context1", then specifying the non-existent "context1" as a context in a task, causes a message to pop up asking to create the new context. However, in this case - no new context is created, and the task is given "Context1".
However, it is possible to create two contexts "context1" and "Context1" - from the context screen ( https://blah/contexts ). Seems pretty stable in choosing the first of the two created though ("context1" in this case).
Related - creating a context "Context1", then specifying the non-existent "context1" as a context in a task, causes a message to pop up asking to create the new context. However, in this case - no new context is created, and the task is given "Context1".
I think I fixed the issue of the original reporter with #1025. When you have context1 and Context1 they can both be selected as a context and it gets saved correctly.
I am still able to reproduce Orlando's use case.
the problem is that
returns "Context1"
I am still able to reproduce Orlando's use case.
the problem is that
select * from contexts where name='context1'
returns "Context1"