Anthony/Warning-Tracker-Followup

[AnthonyWeathers]

Description

Follow up to PR#3978, adding the feature to add a blue square to a user, through choosing to issue a blue square through the warning trackers, both on the dashboard and on the user profile.

Related PRS (if any):

This PR is related to PR#1938 backend PR.

…

Main changes explained:

• Updated PermissionsConst.jsx to rearrange some permissions and remove a no longer used one by request.
• Updated UserProfile.jsx and Warnings.jsx mostly to add ability to create a new bluesquare through the Issue Blue Square option on the warning trackers introduced by PR#3978
• Updated UserProfileModal, added a space between Created Date and the date the blue square was created, assuming a created date if it was manually made. Then commented out the disabled value for the Both button for the special warning trackers on the Profile page when clicking on a bluesquare.
• Updated PermissionListItem with additional values to allow users with Owner role, to add or remove the Blue Square Email Management permission to other users
  …

How to test:

1. check into current branch

2. do npm install and ... to run this PR locally

3. Clear site data/cache

4. log as admin user (owner needed to test being able to add or remove the Blue Square Email Management permission though)

Issue Warnings On Dashboard

5. Find your account or an account you own, that you'll be testing with

6. Click on the Tracking Button (yellow button that should change to show Hide, and display the warnings list below it)

7. Click on the circles of any warning, to simulate adding a warning of that kind for the user

8. Check if you get a success toast with this message: 'Successfully logged and tracked'

9. Repeat for same warning so that when attempting to add a 3rd warning (after having added 2 blue circles), you'd get the modal pop up asking if you'd like to issue another warning or a blue square

10. Issue a warning and verify you get this success toast message: 'Warning successfully logged and sent by email.'

11. Repeat step 10 but issue a bluesquare and verify you get the success toast message: 'Successfully logged and Blue Square issued on profile and by email.' if nothing goes wrong.

User Profile Blue Square Check, Issue Special Warnings, and Test Both Button Blue Squares and Mixed Cases

12. Go to a user profile (preferably yours or another account you made that you can access the email for)

13. Check the blue squares and locate added blue square from the dashboard steps, should look like what's shown in the image. (Note: Only difference between blue squares issued from dashboard will be the name of the warning tracker, indicated by the ""s)

14. Next, click any blue square and remove it by clicking the RBS4NS (Remove Blue Square for No Summary) yellow button, and click Issue Blue Square

15. Verify it removes the bluesquare you chose, then adds a new bluesquare with text explaining it. (This will be different than the blue squares issued from dashboard, so don't mind it)

16. Test with repeating the same step but with the RBS4HCE (Remove Blue Square for Hours Close Enough), ensure the text has the right warning name mentioned

17. Test using the Both, and verify if the summary text accurately describes what you chose. (Ex. If you chose to issue blue square for both warnings, then the summary text should say blue square for both. If you chose blue square for no summary, and warning for hours close enough, then the text will say blue square for no summary, and a warning for hours close enough.

18. Also, verify if the number of times listed in the summary text, matches the Occurrence number of the respective warning

Check Blue Square Email Management permission (Owner users only)

19. Go to Permissions Management

20. Click on a role, or Manage User Permissions and select a user

21. Scroll down to Misc/Unsorted, and find Blue Square Email Management

22. Verify if you can click on it, and change it between Add/Delete

Note

If you have setup email functionality for your local end by following Email sending instructions, then if you issue blue squares or warnings, you will have to modify emailSender function calls, otherwise you may end up emailing other people than just yourself. So adjust them to only be your own emails before testing those features directly. Or you could just set sendEmail to false in the backend env file, as I think that would ensure no email gets sent either.

If you haven't setup your environment for email functionality, then you shouldn't have to worry about accidentally sending emails to people, but double check though incase I forgot something.

[netlify]

✅ Deploy Preview for highestgoodnetwork-dev ready!

Name	Link
🔨 Latest commit	70fcded
🔍 Latest deploy log	https://app.netlify.com/projects/highestgoodnetwork-dev/deploys/693dfbbd982ff90008a61592
😎 Deploy Preview	https://deploy-preview-4502--highestgoodnetwork-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Anusha-Gali]

Hi Anthony,

I have reviwed your PR and followed all the steps mentioned and they are function as per requirement.

[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

[one-community]

Thank you all, merging!