1006807: Fixed the UI and Functionality issues in Employee Management

[SwathiRavi14]

Bug description

Task -1008341: Review corrections - UI/UX & Data Consistency Fixes Across Employee Management, Payroll, PayStub, Leave Report & Organization Modules
[Task - 1006807] Need to test and fix the UI and Functionality issues in Employee Management

1. Overview text must be uppercase.
2. Tab headers must be uppercase.
3. Remove title font family and font weight.
4. Change font weights for filters and grid headers.
5. Match Filters UI with reference image.
6. Remove Employee tab and show grid outside.
7. Fix search and column chooser position mismatch.
8. Add more tooltip details for Employee ID and Name.
9. Change tooltip background color.
10. Remove bold style from grid headers.
11. Align grid headers like HR portal.
12. Reduce dropdown width.
13. Match profile overview header styles with HR portal.
14. Correct UI (font size, weight, line height, row height, icon alignment).
15. Update header icons to match reference.
16. Expand search input to full width while typing.
17. Fix sidebar flicker on collapse.
18. Match leave type colors with HR portal.
19. Remove green border and adjust radius for inputs.
20. Match button and hover styles with HR portal.
21. Update top nav search item template.
22. Fix status color mapping for Employee Management.
23. Correct leaderboard data display.
24. Fix Leave Report badge colors.
25. Correct Paystub title and font size.
26. Fix payroll header-content misalignment.
27. Increase visibility of “Available” label.
28. Rename payroll page title properly.
29. Remove bold from Payroll “Total” column.
30. Organization grid should not load all 1 lakh records at once.
31. Fix button color inconsistencies.
32. Add right padding to column chooser icon.

Root cause

Alignment and styling issues.

Solution description

Fixed the all reported issue with the proper solution

Impact assessment

• Low - Affects a single feature with minimal user impact
• Medium - Affects multiple features or has moderate user impact
• High - Critical functionality or significant user impact

Reason for not identifying earlier

Provide the reason for not identifying the bug earlier.

Areas tested against this fix

• Tested using standard test cases
• Tested against feature matrix. Centralized location
• NA

Breaking changes

• Yes (Tag breaking-issue)
• No

If yes, provide breaking commit details link and migration guidance.

Regression testing

• Verified fix doesn't reintroduce previous bugs
• Checked edge cases and error scenarios'
• NA

Action taken to prevent recurrence

• Added/updated unit tests
• Other (specify): _________________
• NA

Automation status

• BUnit (provide PR link: _________________)
• Playwight (provide PR link: _________________)
• NA

Cross-platform verification

• Blazor Server
• Blazor WASM
• NA

Related issues

Is this issue present in EJ2 or other components?

• Resolved in EJ2 (PR link: _________________)
• Created task for EJ2 (Task link: _________________)
• Needs attention in other components (tag needs-attention-coreteam)
• NA

Output screenshots

NA

API changes

• New API added (API Review task link: _________________)
• Existing API renamed/modified (API Review task link: _________________)
• No API changes

Performance verification

• Verified no memory leaks introduced
• Verified no performance degradation
• Not applicable

Reviewer Checklist

• Code changes follow component guidelines
• All provided information reviewed and verified
• Solution addresses the root cause effectively

[BalajiSGrid]

Code changes are fine