Might have just found the solution to this myself
I figured using gitlab issues to represent requirements would work quite well.
- You can link between issues with: #245 or the related issues feature
- You can comment on each issue
- It’s easy to collaborate with 3rd parties and freelancers
- In the paid starter plan, you can also export all issues to csv. E.g. generate a PDF with tables from the .csv
- Easy sorting with labels: System, Hardware, Mechanical requirement, etc.
- The paid starter plan also has multiple issue boards. This let’s you have an issue board for each requirement category: System, Hardware, Software, etc.
Link to sub requirements
Link to subrequirements e.g. from a System Requirement to Hardware Requirements with related issues:
The weight feature is also perfect, so a contractor can actually fill out how much it will cost him to implement a requirement.
Link to repository content
Often in Requirements you will have 3rd party documents that are in Microsoft Word or any other format. It’s very easy and straight forward to add such documents to the repository and then link it in an issue/requirement.