Skip to content
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

UISACQCOMP-240 Add GroupByOrgActionMenuItem action button for claims #847

Closed
wants to merge 2 commits into from

Conversation

azizjonnurov
Copy link
Contributor

@azizjonnurov azizjonnurov commented Jan 6, 2025

Purpose

https://folio-org.atlassian.net/browse/UISACQCOMP-240

Approach

Screenshots

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

  • I've added appropriate record to the CHANGELOG.md
  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

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.

@azizjonnurov azizjonnurov requested a review from a team as a code owner January 6, 2025 14:19
Copy link

github-actions bot commented Jan 6, 2025

Jest Unit Test Statistics

    1 files  ±0  236 suites  +1   4m 14s ⏱️ -1s
629 tests +2  627 ✔️ +2  2 💤 ±0  0 ±0 
632 runs  +2  630 ✔️ +2  2 💤 ±0  0 ±0 

Results for commit dfeedda. ± Comparison against base commit 76eca3b.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Jan 6, 2025

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit dfeedda. ± Comparison against base commit 76eca3b.

♻️ This comment has been updated with latest results.

@azizjonnurov azizjonnurov changed the title UICLAIM-2 Sort claims by vendor UISACQCOMP-240 Add GroupByOrgActionMenuItem action button for claims Jan 7, 2025
Copy link
Contributor

@usavkov-epam usavkov-epam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no need to store only ui-claims related components in a shared library.

@azizjonnurov azizjonnurov deleted the UICLAIM-2 branch January 8, 2025 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants