-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update existing QT Merit list configuration #2487
Comments
Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @tomlovesgithub @warrensearle |
Please add your planning poker estimate with Zenhub @KoWeiJAC |
This ticket has been blocked by the work of updating the completed screen of Merit list by @warrensearle. |
@nickaddy I think this ticket may have been satisfied by the Merit List MVP 3.0 work. Please could we test/review and either close as completed or identify any remaining work. |
@warrensearle I'm planning the output on a live exercise which concludes in January; will get confirmation from the SET and hopefully be able to close the ticket then. |
Background
The current QT merit list task needs to be reconfigured to display the necessary data on screen, unnecessary content removed, and a download option provided, whilst additional columns not displayed on screen can be optionally selected by Admins to appear on the download.
User Story
As an Admin, I would like to see on screen the candidate name, the z-score and candidate rank and the additional columns specified below included in the download so that I have all the info necessary for candidate feedback.
Benefit(s) to user (if not already clear from User story)
On screen info is limited to what is essential for the merit list, additional info is available in the download.
Feature(s) Description
Acceptance Criteria
It's done when the onscreen and downloaded reports are formatted as described.
Definition of Done
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Nick
The text was updated successfully, but these errors were encountered: