Apply/517 qt analytics - save History and session time #774
Conversation
lloback
requested review from
warrensearle,
mbrookeswebdev,
tomlovesgithub,
KateMJAC and
HalcyonJAC
|
Visit the preview URL for this PR (updated for commit 8286a13): https://jac-apply-develop--pr774-feature-517-qt-analy-yjoal3l5.web.app (expires Fri, 03 Sep 2021 15:30:54 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 |
- Save history - on Exit Modal - on information page - on review - on Situational Judgement - Save session - on skip - on SAve
lloback
force-pushed
the
feature/517-qt-analytics
branch
from
98fc977 to
bd50ca9
Compare
|
This is ready for re-review. |
|
Please refer to #1317. Some final tweaks required to the tickets which run together. |
|
@warrensearle @londonprojects Can someone take a look at this? |
|
@lloback see jac-uk/admin#1317 for changes to make |
* remove name-blind sift and phone assessment from timeline * fix timeline tests * delete commented code Co-authored-by: HalcyonJAC <79906532+HalcyonJAC@users.noreply.github.com>
* Reset PW component with proper validation * check for valid action code
* Display a generic erorr for wrong password or user not found * Update SignIn.vue replicating changes from local copy due to a 403 error * adding lodash as explicit dependency Co-authored-by: warrensearle <warren.searle@judicialappointments.digital>
* inital changes * Update readme * remove commented code Co-authored-by: Warren Searle <warren@precise-minds.co.uk>
* wip * wip * ranked choice changes * remove unrelated changes * remove padding * remove phantom checkbox * add to review page * remove from review page [wrong branch] Co-authored-by: warrensearle <warren.searle@judicialappointments.digital>
- Save history - on Exit Modal - on information page - on review - on Situational Judgement - Save session - on skip - on SAve
…apply into feature/517-qt-analytics
|
Fix the "Saved" "How many times changed answer:" |
|
Hey @KateMJAC @joy-ade please can you test this again in combination with jac-uk/admin#1317 |
|
Approved by UTG |
What's included?
On this ticket we are adding History and Session time to the database. This will be stored and showed on the admin side.
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
There are no changes to test on the apply as this is a backend ticket - we are just storgin information from the user, without any visual interface or interaction.
This needs to be tested in conjunction with the #945 ticket (admin).
Risk - how likely is this to impact other areas?
🟠 Medium risk - this does change code that is shared with other areas
PREVIEW:DEVELOP