Add project-level Requirement object
The first step of &2703 (closed) is to create a Requirement model with associated table in the database.
In it's simplest form, a Requirement should:
- Belong to a project
- Belong to an author
- Have a title
- Have an automatically generated, unique ID
- Exist in the non-FOSS version of GitLab
There is currently no requirement for a description or any more complex relationships.
/cc @mjwood @donaldcook
Edited by Justin Farris