Overview
Glossa allows you to export project requirements to CSV (comma-separated values) format, which can be opened in Excel, Google Sheets, or any spreadsheet application. You can export requirements on their own, or include acceptance criteria and/or user stories in the same export.
CSV exports provide a snapshot of your requirements at a specific point in time and are useful for creating documentation, archiving project data, or performing custom analysis in spreadsheet tools.
Export Options
When you click Export, a panel appears with the following checkboxes:
Include Acceptance Criteria — adds a second table with all acceptance criteria (gherkin, checklist, freeform, and user story formats) linked to each requirement
Include User Stories — adds a second table with only user story-format acceptance criteria linked to each requirement
You can select either, both, or neither. If you select both, the export will contain three tables: Requirements, Acceptance Criteria, and User Stories.
Click Export CSV to download the file.
File Naming
Selection | Filename |
Requirements only |
|
+ Acceptance Criteria |
|
+ User Stories |
|
+ Both |
|
Export Scope
Export includes all requirements currently visible in the table
Respects active filters and views — filter first to export a specific subset
To export all requirements, ensure no filters are applied before exporting
How to Export
Open the project you want to export
Go to the Requirements tab
If you want to export a subset of requirements, apply filters to the table first. To export all requirements, ensure no filters are active.
Click the Export button in the top right of the requirements table
In the Export Options panel, check Include Acceptance Criteria and/or Include User Stories as needed
Click Export CSV
The file downloads immediately to your browser's default download location
Processing time: Instant for small projects (under 100 requirements); may take a few seconds for very large projects (500+ requirements).
CSV File Structure
All exports include a Project Name column as the first field in every table. Exports use a multi-table structure within a single CSV file, with each section labeled by a header row followed by column headers and data rows.
Requirements Table Columns
Column | Description |
Project Name | Name of the Glossa project |
ID | Requirement ID (e.g., PAW-TEST-0001) |
Title | Requirement title |
Slug | URL-friendly version of title |
Description | Full requirement description |
Category | Assigned category (if any) |
Priority | Priority level (critical, high, medium, low) |
Status | Current status (draft, approved, etc.) |
Origin | How the requirement was created |
Created | Date requirement was created |
Acceptance Criteria Table Columns
Included when Include Acceptance Criteria is checked. Contains all AC formats: gherkin, user story, checklist, and freeform.
Column | Description |
Project Name | Name of the Glossa project |
Requirement Title | Parent requirement title |
Requirement Slug | Parent requirement slug |
Slug | AC's unique slug |
Format | AC type (gherkin, user_story, checklist, freeform) |
Content | Full AC text |
Priority | AC priority |
Status | AC status |
Origin | How the AC was created |
Created | Date AC was created |
User Stories Table Columns
Included when Include User Stories is checked. Contains only user story-format acceptance criteria.
Column | Description |
Project Name | Name of the Glossa project |
Requirement Title | Parent requirement title |
Requirement Slug | Parent requirement slug |
Slug | User story's unique slug |
Description | Full user story text ("As a… I want… so that…") |
Priority | Priority |
Status | Status |
Origin | How the user story was created |
Created | Date created |
What's NOT Included in Exports
Citations
Source file links, recording timestamps, and document highlights are not exported. Citations remain accessible in Glossa — reference the requirement there for full source details.
Custom Field Selections
Column selection and ordering cannot be customized. Use your spreadsheet tool to hide or delete unwanted columns after export.
File Attachments
Uploaded files, recordings, and documents are not included. CSV is a text-only format. Download files separately from the Files tab if needed.
Requirement Relationships
Linked requirements, conflict relationships, and merge history are not exported. This data remains accessible in Glossa.
Export Frequency
Exports are manual only — there are no scheduled or automated exports.
Data Accuracy
Exports are a point-in-time snapshot. Changes made after export are not reflected in the file. Re-export to get current data. CSV exports have no live connection to Glossa — editing the CSV does not update Glossa.
Troubleshooting
Export button not visible Confirm you're on the Requirements tab (not Dashboard, Files, etc.). Try maximizing your browser window, refreshing the page, or using a different browser.
File won't download Check that your browser allows downloads from glossapro.ai and that pop-up blockers aren't interfering. For large exports (500+ requirements), wait a bit longer before retrying.
CSV opens with garbled characters Re-download the file and open it with UTF-8 encoding. In Excel: Data → From Text → UTF-8. In Google Sheets: use Import with UTF-8 encoding.
Data missing or incomplete Verify the requirements exist in Glossa, are visible in your filtered view, then re-export. Check that all expected table sections are present in the file.
Export takes too long Very large projects (1,000+ requirements) may take 30–60 seconds. Don't close the browser tab during export.
Limitations
CSV format only — no PDF, Word, or Excel exports
No scheduled exports — must be manually triggered
No citations included
Cannot customize which columns are exported
Static snapshot with no live connection to Glossa
Alternative Export Options
Client Portal: Share requirements directly with clients for review and approval without needing to export and email a CSV. See the Client Portal article for details.
Jira Integration: Use the Jira integration to send requirements directly to Jira for active development work. See the Jira Integration article for details.
Screenshots: For presentations, screenshots of the Requirements table or individual requirements work well in slide decks and documentation.