-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
UIREQ-1188 - Add optional column "Retrieval service point" to requests search list. (follow-up) #1242
Conversation
…into UIREQ-1188
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only change here is to the CHANGELOG. Did something else get lost in the merge?
Quality Gate passedIssues Measures |
Hey @zburke I have updated PR with the same. Could you please re-review now? |
…s search list. (follow-up) (#1242) * UIREQ-1188 - Add optional column 'Retrieval service point' * Male retieval sp column sortable * add unit test * UIREQ-1188 - update changelog.md file. * UIREQ-1188 - duplicate the implementation in deprecated folder
Purpose
UIREQ-1188 - Add optional column "Retrieval service point" to requests search list.
Approach
Refs
Screenshots
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.