Description:
Currently, when creating an assignment, it's possible to assign it to a site, e.g., Chrissy-Test and to group(s), e.g., schools, classes, cohorts, that already sit under that site. This doesn't actually duplicate the assignment.
In watching some users try to make assignments, I think they interpret the current selector as hierarchical, e.g., they think they must select the site, then school, then class to assign only to the class.
Could be better to have a dropdown that says "select by..." with site, school, class, cohort rather than the current tabbed approach?
Functional Requirements:
Regardless of tabs vs dropdown:
- Once a site is selected for an assignment, schools, classes, cohorts that sit under that site should not be selectable ("greyed out"), with a tooltip/popup/error if/when they try to click it that says something like "[school/class/cohort] already in assignment via [site]"
- As above for schools: once a school is selected for an assignment, classes or cohorts that sit under that school should not be selectable in the same manner
- Preference for "greyed out" rather than completely unavailable/invisible in the selector, as this may lead admins to think a group was not properly created, i.e., they should still appear in the selector, just not be usable.
Acceptance Criteria:
QA Testing Requirements:
Platform Elements affected: Dashboard, Tasks/Surveys
User Type: Researcher (but visibilty of correct assignments should also be verified on participant user side)
Checklist
Description:
Currently, when creating an assignment, it's possible to assign it to a site, e.g., Chrissy-Test and to group(s), e.g., schools, classes, cohorts, that already sit under that site. This doesn't actually duplicate the assignment.
In watching some users try to make assignments, I think they interpret the current selector as hierarchical, e.g., they think they must select the site, then school, then class to assign only to the class.
Could be better to have a dropdown that says "select by..." with site, school, class, cohort rather than the current tabbed approach?
Functional Requirements:
Regardless of tabs vs dropdown:
Acceptance Criteria:
QA Testing Requirements:
Platform Elements affected: Dashboard, Tasks/Surveys
User Type: Researcher (but visibilty of correct assignments should also be verified on participant user side)
Checklist