Requirements management with Git repository
Management is quickly becoming a thing in Plan. See &670 (closed). What customers have been emphasizing for RM is change management and traceability. The traceability part is relatively straightforward, because we can link requirements (whatever object it ends up being) to issues and tests that implement said requirements. Change management is a bit harder. Because you need a way to closely manage requirements being changed and see their impact, and possibly even have an approval process. So i’m considering using a project’s repo for exactly that. So you could have a hidden directory .requirements
in a project repo. And then you can manage all your requirements as just simple files. And we would build dedicated UI to make requirements management easy to do, but it would all be driven in the BE by git. For example, each file could represent a single requirement, and you would have special syntax to indicate fields like title, description, etc. in the file itself, similar to the approach of templates almost. So we could re-use merge requests and approvals and maybe tweak them slightly for more RM-friendly use cases.