TODOS
# August 23, 2019
List of affected users based on the query on Step #2 below:

# 1. Investigation with Coachee Mark Jayson
SELECT * FROM users WHERE firstname = 'Mark Jayson';
SELECT * FROM user_roles WHERE user_id = 2423; 

SELECT * FROM users WHERE user_id = 250;
SELECT * FROM user_roles WHERE user_id = 250;

SELECT * FROM admin_session_logs WHERE log_type_id = 27 AND coachee_id = 3084;

# 2. List of affected coachees that have incorrect tagging
SELECT u.user_id, ur.user_role_id, u.firstname, u.lastname, u.coach_id FROM users u
LEFT JOIN user_roles ur ON ur.user_id = u.user_id
LEFT JOIN admin_session_logs asl ON asl.coachee_id = ur.user_role_id
WHERE ur.role = 'COACHEE'
AND asl.admin_session_id IS NOT NULL
AND u.active IS NULL 
AND status = 'active'
AND u.user_id != 2360 # we don't include uy joseph
ORDER BY user_role_id;


# 3. Last known issue with incorrect tagging is create on 2019-08-07
SELECT * FROM admin_session_logs WHERE log_type_id = 27 AND coachee_id = 3094;

# 4. Update all affected users active column to be equal to when the admin tagged them.
UPDATE users SET active = '2019-08-07' WHERE user_id = 2431;
UPDATE users SET active = '2019-08-07' WHERE user_id = 2430;
UPDATE users SET active = '2019-08-07' AND coach_id = 981 WHERE user_id = 2429;

UPDATE users SET active = '2019-08-06' WHERE user_id = 2425;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2424;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2423;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2421;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2420;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2419;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2418;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2417;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2416;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2415;
UPDATE users SET active = '2019-08-06' WHERE user_id = 2414;

UPDATE users SET active = '2019-07-16' WHERE user_id = 2413;

The fix for this issue was deployed on August 08, 2019.

# August 7, 2019

- CMS
- [x] Add reason.
- [ ] Coach Report 0 N/A issue.
- [x] All coachees / filter no coach.

- SITE
- [x] Add label tag request: Kindly declare the official effective date of movement
- [x] Percentage on YTD.

# August 3, 2019

**HOTFIX**
https://github.com/cacherojordan/c2g/commit/2da83fe967981e704be4c5188dbc43ec7dffa69b?diff=unified
- [x] Wrong reflection of date when tagging
> *Note: I've Manually updated the data of the affected users in the production database mentioned in the email.*

**CMS**
- [x] Reason field show on panel
- [x] active or resigned status on user lists check for there status if disabled or deleted is equal to resigned
> *Just run the `/Migrate/updateuserstatus`*
- [x] 0 and N/A changes for all reports like growsession
> *Please double check, this was already completed before. Or please specify what report needs to be updated.*
- [x] remarks on coaching effectiveness should be bulleted to be filtered, cause they cannot filter when using space or comma for the remarks field
> *Done but only tested in browser, please check in excel.*
- [x] for coaching report the ytd should not be divided by 12, instead count the number of months before it became n/a then divide it to that

**SITE**
- [x] dropdown, coachee ..cmg wide no need by department filter , listCoachees model, to put on staging later
- [x] remove paternity leave on dropdown reason
- [x] enable current date picking for date picking on tagging
- [ ] tooltip / label for comment on tagging
> *What part? On Create Tag Request it already has a label.*
- [x] Tagging, tag action should move forward even if pending wayforward
> *The requirement before is to not allow tagging if has pending wayforward. That is now removed.*
- [x] effective date change date format to ex. 09/01/2019 on tagging view
- [ ] all coachees filter no coach
- [x] add this page from panel to ui page , https://staging-panel.globec2g.com/coachee_scoreboard/coachee/2019/1 design will be given

**API**
- [x] & is not accepted still for login page need to update api
> *Working, tested on postman. Maybe a frontend issue. Or please specify the steps.*