EPMRPP-103964 || Add sorting by name for All users page

[allaprischepa]

PR Checklist

• Have you verified that the PR is pointing to the correct target branch? (develop for features/bugfixes, other if mentioned in the task)
• Have you verified that your branch is consistent with the target branch and has no conflicts? (if not, make a rebase under the target branch)
• Have you checked that everything works within the branch according to the task description and tested it locally?
• Have you run the linter (npm run lint) prior to submission? Enable the git hook on commit in your IDE to run it and format the code automatically.
• Have you run the tests locally and added/updated them if needed?
• Have you checked that app can be built (npm run build)?
• Have you checked that no new circular dependencies appreared with your changes? (the webpack plugin reports circular dependencies within the dev npm script)
• Have you made sure that all the necessary pipelines has been successfully completed?
• If the task requires translations to be updated, have you done this by running the manage:translations script?
• Have you added the link to the PR in the Jira ticket comments?

Visuals

Summary by CodeRabbit

• Refactor
  • Updated the default sorting column and related keys from camelCase to snake_case for user full name fields.
  • Adjusted table display and sorting functionality to use the updated snake_case column name.

[coderabbitai]

Walkthrough

The changes update the user property naming convention from camelCase (fullName) to snake_case (full_name) across both constants and component logic. This affects default sorting, search keys, and data mapping in the all users list table. Additionally, the sorting configuration is updated to use a new SORTING_KEY constant.

Changes

File(s)	Change Summary
app/src/controllers/instance/allUsers/constants.js	Renamed constants from camelCase (fullName) to snake_case (full_name) for sort/search columns.
app/src/pages/instance/allUsersPage/allUsersListTable/allUsersListTable.jsx	Updated data mapping and column keys from fullName to full_name; added sortingKey to config.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AllUsersListTableComponent
    participant Constants

    User->>AllUsersListTableComponent: Loads user list page
    AllUsersListTableComponent->>Constants: Fetches DEFAULT_SORT_COLUMN, SORTING_KEY
    AllUsersListTableComponent->>AllUsersListTableComponent: Maps user data using 'full_name'
    AllUsersListTableComponent->>AllUsersListTableComponent: Configures sorting with 'full_name'
    AllUsersListTableComponent-->>User: Displays sorted user list by full name

Loading

Suggested reviewers

• AmsterGet
• BlazarQSO
• maria-hambardzumian

Poem

In code where users' names reside,
A subtle shift, now snake_case applied.
From fullName to full_name we go,
Sorting and searching in a neat new flow.
The table refreshed, the mapping just right—
A rabbit hops on, coding delight! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 48b0214 and 6118a71.

📒 Files selected for processing (2)

• app/src/controllers/instance/allUsers/constants.js (1 hunks)
• app/src/pages/instance/allUsersPage/allUsersListTable/allUsersListTable.jsx (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• app/src/controllers/instance/allUsers/constants.js
• app/src/pages/instance/allUsersPage/allUsersListTable/allUsersListTable.jsx

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Call feature Docker build / Build and export to AWS ECR
• GitHub Check: build (20)
• GitHub Check: build (20)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch fix/EPMRPP-103964-add-sorting-by-name-for-all-users-page

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.53%. Comparing base (0adca97) to head (6118a71).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #4422   +/-   ##
========================================
  Coverage    66.53%   66.53%           
========================================
  Files           85       85           
  Lines          983      983           
  Branches       139      139           
========================================
  Hits           654      654           
  Misses         298      298           
  Partials        31       31           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[allaprischepa]

Force pushed to resolve out-of-date issue

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud