Feature #176
search with user-controlled case-sensitivity
| Status: | Closed | Start: | 07/07/2009 | |
| Priority: | Normal | Due date: | ||
| To: | Paul Beckingham | % Done: | 100% |
|
| Category: | core | Spent time: | 16.00 hours | |
| Target version: | 1.9.0 - Kuwagata | Estimated time: | 3.00 hours | |
Description
In task 1.7.1 keyword searches were case-insensitive. In task 1.8.0 they became case-sensitive. Both are equally useful depending on the circumstances. The user should have a choice in which method is used.
Example tasks where one might want to search for "bill":
Pay monthly bills
Pay Bill back the money I owe him
I may want to get a listing of tasks that aren't related to a person named Bill. I may want a listing of tasks that are related to a person named Bill. I may want a listing with both of these tasks because I simply don't recall how they were entered at the time.
History
Updated by David Patrick 387 days ago
Personally, I favour "upper-case sensitivity" where searches in all lower-case are case insensitive, but the use of any upper-case character in a search string forces the search to be case-sensitive.
Updated by David Patrick 375 days ago
- To changed from David Patrick to Paul Beckingham
Updated by Paul Beckingham 325 days ago
- Target version changed from 2.0.x - Katana to 1.9.0 - Kuwagata
Updated by Paul Beckingham 182 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Estimated time set to 3.00
Triggered by the
search.case.sensitive=yessetting in .taskrc