Prevent project transfer if new group isn't selected
Currently, when you opt to Transfer a Project
to another group, you are expected to select the new project from a dropdown.
I see three problems happening with this workflow:
- If you're moving quickly, it isn't that obvious that you're supposed to select a new group before selecting this.
- Even if you don't select a new group, you can still click the submit button, type in your project name, and confirm that you want to transfer projects.
- When the form is submitted without selecting a new group, a very vague error (
is invalid
) is returned.
Here's what it looks like:
Proposed Solutions:
- Add copy that explicitly informs the user that they must select a new Group. Perhaps instead of just a subtitle
Transfer project
, we make the titleTransfer project to new group
, and add a description like "Please select the group you want to transfer this project to in the dropdown to the right.". - Prevent the user from transferring the group if they have not selected a new Group.
- Have a more verbose error message. As it is, it's a ~bug .
I haven't looked carefully at other forms on this page, but I'm guessing there are other configuration options should be validated on the front-end as well.
Proposed UX
The dropdown control is blank by default (as you need to chose a namespace to transfer to). The 'Transfer' button is disabled until an option is chosen in the dropdown control.
If you somehow manage to still access this endpoint, we should have a more descriptive error message.