What problem are you trying to solve with Submitty
Many of the fields in the web interface for a electronic gradeable could be saved in the config.json. Many fields are required to set up the gradeable and our institution has different defaults then submitty.

Describe the way you'd like to solve this problem
Additional fields should be allowed to be defined in the config.json. These additional fields would be helpful:

• Are students uploading files or submitting to a Version Control System (VCS) repository?
• Is this a team assignment?
• Will any or all of this assignment be manually graded (e.g., by the TAs or the instructor)?
• Manual grading
  • All manual grading settings
• Should students be able to view submissions?
• How many late days may students use on this assignment?
• What syllabus category does this item belong to?

Only settings not in the gradeable config.json would be:

• What is the title of this gradeable?:
• What is the URL to the assignment instructions? (shown to student)
• What is the unique id of this gradeable? (e.g., hw01, lab_12, or midterm):

Describe any potential alternatives you'd tried to solve the problem
The copy gradeable does not work due to slight differences between each assignment. It would be nice to have all of the details in the config.json.

Additional context
It could be that the config.json only gives defaults that override the submitty defaults. This would help set up the REST API (#300) to have a clean new gradeable endpoint.