<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Description As important as it is for teams to be able to import requirements, it's equally important for them to be able to export requirements for delivery or collaboration with external organizations. ## Proposal ### MVC To start with, exporting to a standard format (such as CSV to be compatible with the import functionality) would suffice. We would want to export Requirement ID, Title, and Description (implementation in progress). ### Further Iterations Below are a list of ideas to support in further iterations: * Be able to export additional items such as created date, created by, last modified date, lost modified by, and verification status. This would ideally be selectable so exports could be customized * Add import functionality for new features we add to requirements (such as labels)