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

Change of panel packs location #1222

Closed
4 of 14 tasks
nickaddy opened this issue Oct 4, 2024 · 4 comments · Fixed by #1315
Closed
4 of 14 tasks

Change of panel packs location #1222

nickaddy opened this issue Oct 4, 2024 · 4 comments · Fixed by #1315
Assignees

Comments

@nickaddy
Copy link
Contributor

nickaddy commented Oct 4, 2024

Background

Rather than creating panel packs in the root folder on Production and SETs having to copy them across to the exercise folders, creating them directly in the exercise folders will be more efficient. It will also potentially allow other benefits, e.g. being able to automatically set the folder permissions based on the panel set-up.

In order to facilitate this change, we have an agreed nomenclature for the exercise folder, which will be the exercise reference number, e.g. JAC00184.

Note: Admins will need to be informed that they have to share the folder with the Digital platform email address and this process will have to be embedded.

User Story

As an Admin, I would like panel packs to be created directly in the exercise folder so that I don't have to copy them there.

Benefit(s) to user (if not already clear from User story)

Allow panellists to be automatically given permission to access the panel packs folder and subfolders.

Feature(s) Description

  • Panel packs should be created in the exercise root folder which has the name of the exercise reference
  • A top level folder for Panels should be created and, within that folder, a subfolder 'Sift' or 'Selection day' created depending on which task panel packs are being prepared for and, within that folder, panel pack folders created as per panel set-up (number of panels, candidate allocation to panels)
  • If the root folder is not found, an error message is generated: 'Folder not found - please rename root exercise folder according to the reference number of the exercise, i.e. JAC00XXX
  • Inform Nick of the email address used by the platform so that he can inform Admins that this Google address needs to be added to root folders to allow Digital platform access

Acceptance Criteria

It's done when:

  • Panel packs are created in sub-folders within the exercise folder
  • Panel packs for sifts are created in a sub-folder Panels > Sift
  • Panel packs for selection days are created in a sub-folder Panels > Selection day
  • An error message appears if Admins have not names exercise root folder correctly

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.)

Feature Champion

Nick

@tomlovesgithub
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC

@tomlovesgithub
Copy link
Contributor

what happens to existing panel packs?

@nickaddy
Copy link
Contributor Author

@tomlovesgithub They can stay where they are. We'll be looking to start this from once we release the new feature. As it stands, teams copy panel packs generated across to the exercise folder. This will obviate the need to do that and also reduce storage space used on G Drive.

@HalcyonJAC
Copy link
Contributor

HalcyonJAC commented Jan 31, 2025

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

Successfully merging a pull request may close this issue.

3 participants