WP-547: case insensitive email in GET tickets #944
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
In cases, where email in RT Ticketing system is different case vs email address stored in Core Portal user list, a bug shows up where ticket list shows up, but viewing details of the ticket (get_ticket call) fails on access control in rtUtil.djangoRT module.
When searching for tickets, rtUtil.djangoRT uses Requestors__exact search. For this search, RT uses case insensitive. So, the user is able to see all the tickets.When opening a specific ticket, portal does case sensitive check for access to the ticket in requestors and cc fields.
RT search depends on the DB settings for case sensitivity. Search api
__exact
converts to=
in sql.Related
Changes
Testing
UI
Notes