We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11051
Created by elippmann on 2016-01-28 14:00:45 +00:00
Assignee: aklimov Status: Resolved (closed on 2016-02-11 12:57:28 +00:00) Target Version: 2.2.0 Last Update: 2016-02-11 12:57:28 +00:00 (in Redmine)
Changesets
2016-02-10 15:21:19 +00:00 by aklimov 001c63e
Don't rely on case sensitive usernames in preferences stored in INI files refs #11051
2016-02-10 15:22:51 +00:00 by aklimov a5924f2
Don't rely on case sensitive usernames in navigation items stored in INI files refs #11051
2016-02-11 10:48:50 +00:00 by aklimov 809861c
FilterExpression: make case insensitive matching possible refs #11051
2016-02-11 10:59:57 +00:00 by aklimov 8ebc92e
Implement FilterMatchCaseInsensitive refs #11051
2016-02-11 11:00:33 +00:00 by aklimov aae7c11
Implement FilterMatchNotCaseInsensitive refs #11051
2016-02-11 11:12:25 +00:00 by aklimov 0791323
Navigation items listing: don't rely on case sensitive usernames stored in INI files refs #11051
2016-02-11 12:29:00 +00:00 by aklimov ea9bc6c
Conform to coding guidelines refs #11051
2016-02-11 12:30:34 +00:00 by aklimov e97426e
FilterExpression: document getCaseSensitive() and setCaseSensitive() refs #11051
2016-02-11 12:32:42 +00:00 by aklimov 8493540
FilterExpression: provide default value for setCaseSensitive() refs #11051
2016-02-11 12:54:53 +00:00 by aklimov d34b0f0
Merge branch 'bugfix/preferences-and-navigation-items-stored-in-ini-files-rely-on-case-sensitive-usernames-11051' fixes #11051
The text was updated successfully, but these errors were encountered:
Updated by jmeyer on 2016-02-10 12:55:24 +00:00
Sorry, something went wrong.
Updated by aklimov on 2016-02-11 11:15:17 +00:00
Updated by jmeyer on 2016-02-11 12:20:08 +00:00
Updated by aklimov on 2016-02-11 12:35:00 +00:00
Updated by aklimov on 2016-02-11 12:52:49 +00:00
Updated by aklimov on 2016-02-11 12:57:28 +00:00
Applied in changeset d34b0f0.
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11051
Created by elippmann on 2016-01-28 14:00:45 +00:00
Assignee: aklimov
Status: Resolved (closed on 2016-02-11 12:57:28 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-11 12:57:28 +00:00 (in Redmine)
Changesets
2016-02-10 15:21:19 +00:00 by aklimov 001c63e
2016-02-10 15:22:51 +00:00 by aklimov a5924f2
2016-02-11 10:48:50 +00:00 by aklimov 809861c
2016-02-11 10:59:57 +00:00 by aklimov 8ebc92e
2016-02-11 11:00:33 +00:00 by aklimov aae7c11
2016-02-11 11:12:25 +00:00 by aklimov 0791323
2016-02-11 12:29:00 +00:00 by aklimov ea9bc6c
2016-02-11 12:30:34 +00:00 by aklimov e97426e
2016-02-11 12:32:42 +00:00 by aklimov 8493540
2016-02-11 12:54:53 +00:00 by aklimov d34b0f0
The text was updated successfully, but these errors were encountered: