Skip to content

investigate frontend functionality for user/setup_request feature #13

@stevenolen

Description

@stevenolen

ohmage/server#865

The expected flow would modify these portions of the classes tool:

  • Do no notify users on #classes visit that they do not have these privileges, instead check on Create Class button click. This also enables simple participants to see their class list without scary red error messages!
  • if user doesn't have user/setup/class/setup privileges, redirect to a new request form.
  • perhaps, if we like this idea, don't redirect to the form if they already have a pending request, just inform them their request is still pending.
  • Form elements (update when we land on exact specs):
    • username required, disabled and pre-filled with logged in user's username
    • email required, pre-fill with user's email on file if it exists
    • study_start_date required, perhaps a tool tip to ask to approximate?
    • study_duration: required, dropdown: 1-3months, 3-6months,6-12months, 12+ months
    • study_description: required, free text
    • study_user_count: required, dropdown: 1-50, 50-100,100-200,200+
  • Perhaps we also want to show them the policy mentioned in the issue on this page??

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions