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

Add "safety test" page #34

Open
18 tasks
lvps opened this issue Oct 30, 2021 · 1 comment
Open
18 tasks

Add "safety test" page #34

lvps opened this issue Oct 30, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@lvps
Copy link
Member

lvps commented Oct 30, 2021

Multiple tables/lists:

  1. People to schedule
  2. People scheduled for each day (similar to WEEEHire inverviews table)

Table 1: People to schedule:

  • Only show users which have a matricola (or some other attribute which allows us to exclude system accounts) AND do not have a safety test date
  • Display: name, surname, matricola
  • Checkbox for "schedule requested" (email sent), linked to a new LDAP attribute to be created*
  • "Schedule requested" button
  • Scheduled day (always empty, if set they do not appear in this table)
  • A "toggle all" button which works client-side only (useful if we want to to do "all but one")
  • SIR download button
  • Table should be sortable client-side, at least for name, surname, matricola (use surname by default/server-side), but the usual library messes up JS even handlers so it's not a top priority

After the table:

  • Email template for all users without "schedule requested"

Table 2: People scheduled for each day

  • Only show users which have a safetyTestDate attribute AND (are NOT locked AND have signed the SIR)*
  • Multiple "headers" for different days, or multiple tables
  • Display: name, surname, matricola, groups
  • Checkbox for "SIR signed"
  • Checkbox for "locked"
  • Scheduled day (may be redundant, but it's useful if we want to quickly change the date) and some way to completely unschedule the test (big red button? deleting the date?)
  • SIR download button
  • "Save" button at the end
  • Table should be sortable client-side, at least for name, surname, matricola (use surname by default/server-side)

The new LDAP attribute may be something more than a boolean. Something like safetyTestStatus: (no|todo|requested), "scheduled" is implicit from the presence/absence date.

@lvps lvps added the enhancement New feature or request label Oct 30, 2021
@lvps
Copy link
Member Author

lvps commented Apr 6, 2022

Send email to weeeino with the date or via bot

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

No branches or pull requests

1 participant