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

PIMS-1605 Custom Sort for User Status #2424

Merged
merged 5 commits into from
May 31, 2024
Merged

Conversation

TaylorFries
Copy link
Collaborator

@TaylorFries TaylorFries commented May 30, 2024

🎯 Summary

PIMS-1605:

Wrote custom sort for user status such that:

  • on hold users will be first
  • disabled and denied users will be on the bottom.

If there is a better sorting option please let me know.

Testing

Load and run branch locally. Navigate to user table and test out flipping arrow up and down, setting random users to onhold and seeing results.
If Status is not showing as the initial sort option try clearing browser data and reloading.

🔰 Checklist

  • I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.
  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation where required.
  • I have tested my changes to the best of my ability.
  • My changes generate no new warnings.

Copy link

🚀 Deployment Information

The React APP Image has been built with the tag: 2424. Please make sure to utilize this specific tag when promoting these changes to the TEST and PROD environments during the APP deployment. For more updates please monitor Image Tags Page on Wiki.

@TaylorFries TaylorFries merged commit f8b9613 into main May 31, 2024
6 checks passed
@TaylorFries TaylorFries deleted the PIMS-1605-default-sort-tables branch May 31, 2024 17:03
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