#1001
  • Created on
    2010-02-25 03:24
  • Reported by
    nshram
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    2.0
  • Plan Level
    -
  • Due Date
    -

Attachments

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:

  1. 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.

  1. Tracks is not allowing such a default context to be changed to blank. It gets reset to the originally defined, first letter capitalised context.

  1. 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.".

  1. I tried context "work" which gets converted to "Work"
User picture
  on 2010-03-19 13:10 *
By lrbalt
Severity changed from normal to minor
Milestone set to 1.7.1
Severity changed from normal to minor
Milestone set to 1.7.1
It is intended behaviour that contexts are capitalized. but it is wrong that Work and work are then different.
User picture
  on 2010-04-23 13:09 *
By lrbalt
Milestone changed from 1.7.1 to 2.0
Milestone changed from 1.7.1 to 2.0
User picture
  on 2010-05-08 23:45 *
By epall
I'm not seeing the behavior described in this ticket in the git master branch. Invalid?
User picture
  on 2010-05-17 20:19 *
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".
User picture
  on 2010-05-18 01:16 *
By epall
Hmm. So user error can cause strange behavior. What would make sense for Tracks to do to avoid this confusion?
User picture
  on 2010-08-06 08:42 *
By lrbalt
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

select * from contexts where name='context1'


returns "Context1"
User picture
  on 2010-08-06 08:45 *
By lrbalt
Related association with ticket #1058 was added
User picture
  on 2010-08-06 08:47 *
By lrbalt
Related association with ticket #1059 was added
User picture
  on 2010-08-06 08:47 *
By lrbalt
Status changed from New to Fixed
Status changed from New to Fixed
I'm closing this ticket, but created two new. One for the issue of Orlando and on for the second issue of the original reporter.