Docs feedback - feature proposal: Epic field should be included in CSV export

Problem to solve

The Epic field for issues/user stories should be included in exported CSVs

Intended users

All

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->

Further details

For creating reports/slicing & dicing issues externally (i.e. in Excel), it would be great to do without having to manually update each individual issue with a data point that is already present in Gitlab

Proposal

Add the Epic field as a column for exported CSVs

Permissions and Security

No additional requirements above what already exists when exporting issues

Documentation

Testing

For issues that have been exported in CSVs, the Epic field/column should be present and contain the same data for a row/record that is present when viewing that issue in Gitlab

What does success look like, and how can we measure that?

The Epic field is present in exported CSVs

Links / references