Customer requests

Within NHS jobs there is a facility where the HM can add in desired and required skills and experience. When the candidate applies for a job they are directed to complete a specific part of their application against each skill or experience. So it really segments the application process. The HM can then review and score in NHS jobs each applicant against each answer. So it gives them real granularity on the candidates application. Leeds Community healthcare would like to replicate this process. It's similar to score card but being able to build a questionnaire on the fly at job create and have the score card have a direct relationship with each answer.

A client only want certain user types to be able to invite candidates to integrations, however currently all integration perms are global. As a SU I want to be able to limit which of my user types can invite a candidate to an integration So that I can stop people using this feature who should not have access. Note: this should be a user type permission and not the global permission it is now

Placeholder ticket for Capita / Security Watchdog integration

Feedback on job req is that we should hide non mandatory fields that have been set up in a template, to make the process appear slicker to a recruiter who is completing the requisition form. This is similar to the work we are doing to hide locked fields on job create, but instead of hiding the locked fields, we are hiding the non mandatory ones. this would need to be permission based, so that some user types can see and complete all fields but others would be limited to seeing only the fields they need to complete.

There are campaign filters on Job booster, but there is no ability to provide number of Clicks, applicants, money spent or Job campaigns created in a chosen period of time. (from date... to date...) or last 3,6,9,12 months.

Having a visible candidate ID number when opening a process questionnaire As a recruiter I wish to see the candidate ID at the top of any process questionnaire So that I can check I am completing the questionnaire about the correct canddiate

Adding a job req should come before create a job on the jobs drop down list.

When you create a job req and it is approved, if you have disabled the ability for that user type to create a vacancy - that user type still has the 'create' button, which although does nothing is not a good experience. This button should be either: a) Tied to the perm that disables creating a vacancy. b) A perm on its own.

Placeholder for detailed requirement for improvements to notes and tasks

A client would like the option to hide the ability of onboarding workflows to be available to hiring managers. This was on DKs previous roadmap