projects and tags are case sensitive
Bug #197037 reported by
Brian Murray
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bug Helper |
Fix Released
|
Low
|
Unassigned |
Bug Description
revision 205 of the main branch
Using the '--status' filter requires you to use the right case for the status - you have to use 'New' and not 'new'. It should be possible to use either one. I'm guess the same thing is true for importance and it shouldn't be either.
Changed in bughelper: | |
importance: | Undecided → Low |
Changed in bughelper: | |
status: | In Progress → Triaged |
Changed in bughelper: | |
status: | Triaged → In Progress |
summary: |
- bug statuses are case sensitive + projects and tags are case sensitive |
Changed in bughelper: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
<thekorn> currently all string options are case sensitive,
<thekorn> bdmurray, do you thing we should change all of them, or just importance/status
<bdmurray> thekorn: I'm not certain about all of them because of launchpad. Can you have tags like 'foo' and 'Foo'? Projects too?
<thekorn> bdmurray, projects are just lowercase
<thekorn> and tags are also lowercase
<bdmurray> okay, then doing everything sounds good
<bdmurray> it'll help with reporter and lastcomment user too
<thekorn> ok
I'll try to find a solution for bug{helper,numbers} (maybe also buginfo) which does not change tons of code.
First idea, without looking at the code is hooking in OptionParser.
Markus