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.

Sign up for GitHub

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

Jump to bottom

Request form: Group fields by require now vs required later. #825

Open
dvenprasad opened this issue Apr 19, 2021 · 0 comments
Open

Request form: Group fields by require now vs required later. #825

dvenprasad opened this issue Apr 19, 2021 · 0 comments
Labels
design tickets that relate to creating/modifying design Medium Priority user feedback feedback received from users via evals or emails or other comm channels

Comments

@dvenprasad
Copy link
Member

Context

Came up during beta testing

Problem or idea

IRB and MTA are always required to be provided later. Currently, when those are required, they are placed between project abstract and shipping. It kinda breaks the flow of activity i.e., users are in filling mode and then they have to stop and absorb that MTA and IRB are required later and then continue filling. We should group them by filling and absorbing so that the flow is not interrupted.

Solution or next step

I will redesign the form
@dvenprasad dvenprasad added design tickets that relate to creating/modifying design Medium Priority user feedback feedback received from users via evals or emails or other comm channels labels Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design tickets that relate to creating/modifying design Medium Priority user feedback feedback received from users via evals or emails or other comm channels
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dvenprasad