#1059
  • Created on
    2010-08-06 03:46
  • Reported by
    lrbalt
  • Status
    Migrated
  • Priority
    Lowest (5)
  • Assigned to
    -
  • Milestone
    2.3
  • Plan Level
    -
  • Due Date
    -

Attachments

Finding a context is case insensitive while Tracks assumes case sensitivty

from the comments of #1001

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-08-06 03:47 *
By lrbalt
Related association with ticket #1001 was added
User picture
  on 2011-07-09 10:35 *
By lrbalt
Priority changed from Normal (3) to Low (4)
Priority changed from Normal (3) to Low (4)
User picture
  on 2011-10-21 17:16 *
By u2ix
Assigned to set to u2ix
Status changed from New to Accepted
Assigned to set to u2ix
Status changed from New to Accepted
Can't reproduce this. It seems to be possible to create ["Context1", "context1"].

But I think it would be better if it's not possible. So should I make it case insensitive?
User picture
  on 2011-10-22 03:40 *
By lrbalt
I am not sure, perhaps there are use cases where case sensitivity is warranted. Perhaps discus it on the mailing list? If no one needs case sensitivity, make it insensitive...
User picture
  on 2011-10-26 20:18 *
By maddentim
My vote would be insensitive (but I am not trying to be insensitive to the sensitive :)
User picture
  on 2011-10-27 04:41 *
By lrbalt
In my personal situation I do not have two contexts with same name and different cases. But I would like to be able to create a context where I could set the case, i.e. I'd like to add "@Home" or "@IDE" and not have Tracks change it into something else...
User picture
  on 2011-11-09 09:15 *
By u2ix
Type changed from defect to enhancement
Severity changed from normal to minor
Component changed from Functionality (app) to User interface (js)
Priority changed from Low (4) to Lowest (5)
Type changed from defect to enhancement
Severity changed from normal to minor
Component changed from Functionality (app) to User interface (js)
Priority changed from Low (4) to Lowest (5)
So the survey on the mailing list resulted in:
Tracks can ignore cases on adding a TODO to an existing context.

Of course nobody wants to make all contexts lower case or something like that! This is only for adding a TODO to an existing context without having to look at capitalize everything right.
So if you have an existing context @IDE* and you add a new todo and write *@ide* it should be added to the existing context *@IDE*.

*So new contexts can still be capitalized and are case sensitive.

I implement this as part of #1188.
User picture
  on 2012-01-30 03:37 *
By lrbalt
Milestone changed from 2.1 to 2.2
Milestone changed from 2.1 to 2.2
User picture
  on 2012-04-06 07:01 *
By lrbalt
Status changed from Accepted to New
Status changed from Accepted to New
User picture
  on 2012-04-06 07:18 *
By lrbalt
Assigned to changed from u2ix to -none-
Assigned to changed from u2ix to -none-
User picture
  on 2012-04-16 06:37 *
By lrbalt
Milestone changed from 2.2 to 2.3
Milestone changed from 2.2 to 2.3
User picture
  on 2014-06-25 12:11 *
By zoombody
Migrated to GitHub issue #1059
User picture
  on 2014-06-25 12:36 *
By zoombody
Status changed from New to Migrated
Status changed from New to Migrated