Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove CV as assessment option from Admin/Apply #2486

Closed
5 of 11 tasks
nickaddy opened this issue Jul 11, 2024 · 7 comments
Closed
5 of 11 tasks

Remove CV as assessment option from Admin/Apply #2486

nickaddy opened this issue Jul 11, 2024 · 7 comments
Assignees

Comments

@nickaddy
Copy link
Contributor

nickaddy commented Jul 11, 2024

Background

Following a decision at the July board, CVs will no longer be an assessment tool used on selection exercises (they were previously used on Senior/Leadership exercises only.) Instead, we have included a career highlights section on the candidate self-assessment form. Candidates' responses will be extracted from the .docx document, word counted and fed through to Application view as per the answers to the selected Skills & Abilities questions. Ideally this work will be completed prior to the launch of JAC00213 on 25 July and would apply to all future exercises, including those currently in Draft status.

Clearly, any past or current exercises using CVs should be unaffected by this change.

Pls note: the Career highlights section has already been included as an option in the skills and competencies dropdown under Assessment options.
image.png

User Story

As the Ops team, I would like the CV upload option to be replaced by the career highlights section so that candidates still have the option to provide relevant information on their suitability.

Feature(s) Description

  • Remove CV as an option from Assessment options

image.png

  • Ensure that candidates are not presented with an option on Apply to upload a CV in any circumstances
  • Test that candidates can input content to the Career Highlights question on the SA upload and are given the opportunity to edit, having been informed of the word count, before submitting
  • Test that the content added under Career Highlights in an upload is correctly word counted and pulled across to Application view on Admin
  • Confirm that this covers all instances related to CVs?

Acceptance Criteria

It's done when Admins are no longer able to add CV as an Assessment option and candidate are unable to upload a CV but instead complete the Career highlights section of the SA upload.

Definition of Done

  • User stories/acceptance criteria met
  • Internal reviews passed (feedback actioned)
  • User testing passed
  • Relevant technical documentation updated
  • User guidance updated
  • Deployed and merged without errors

User Testing Steps

Specify for users what is being tested (but not how to test it.)

@nickaddy
Copy link
Contributor Author

@drieJAC
Copy link
Contributor

drieJAC commented Jul 12, 2024

@nickaddy We should add a ticket to the backlog so that in 6 mths we should remove any code related to uploading cvs.

@drieJAC
Copy link
Contributor

drieJAC commented Jul 12, 2024

Developer Tasks For This Ticket:

  • Remove the CV option on Admin
  • On Apply if the CV option is present then display the CV section otherwise dont
  • Check that the career highlights display when added to the SA template

@nickaddy
Copy link
Contributor Author

@HalcyonJAC Are the other aspects of this ticket going to be picked up in another PR?

@HalcyonJAC
Copy link
Contributor

@nickaddy I have created an exercise to test that candidates can input content to the Career Highlights question on the SA upload. It works fine. Here is an exercise on Dev if you would like to test it.

@nickaddy
Copy link
Contributor Author

@HalcyonJAC That all works as it should. I noticed a minor display issue on Apply; when you are prompted to review your application, some of the meta-data is presented at the top of the self-assessment content section:
image

@HalcyonJAC
Copy link
Contributor

@nickaddy Thank you for spotting that. A PR has been created to fix it. Could you test it, please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants