Update names on change #12
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Update: turns out it's definitely queue's fault, as revealed by further testing with It is therefore highly likely that this caching behaviour (where names are never updated) is the root cause of this issue, but I am performing some extra testing to confirm (by finding people I know who've never ever signed into queue, to see whether it will pull in a preferred name on the first login). This process takes some time (for name changes etc.) but I will return here once that's done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Might close #11.
It appears that Users in the system are never updated; students are able to change their "preferred name" once per day via SInet, so this is not a correct assumption.
This is blocked on ITIG Helpdesk responding to my query about the
X-KVD-Payloadname field - the documentation suggests it should be the preferred name. If zones is working as documented, then the problem falls back to the Queue app, and this is the likely culprit.This PR will be updated with alternative changes to support preferred names if necessary.