Add latest changes from gitlab-org/gitlab@16-4-stable-eev16.4.0-rc42

1 files changed, 78 insertions, 73 deletions

diff --git a/doc/user/project/issues/csv_export.md b/doc/user/project/issues/csv_export.md
index 86370cab963..34a9b69038b 100644
--- a/doc/user/project/issues/csv_export.md
+++ b/doc/user/project/issues/csv_export.md
@@ -1,97 +1,102 @@
 ---
-stage: none
-group: unassigned
+stage: Plan
+group: Project Management
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
 # Export issues to CSV **(FREE ALL)**
 
-> Moved to GitLab Free in 12.10.
-
-You can export issues as CSV files from GitLab, which are sent to your default
-notification email address as an attachment.
-
-**Export Issues to CSV** enables you and your team to export all the data
-collected from issues into a **[comma-separated values](https://en.wikipedia.org/wiki/Comma-separated_values)** (CSV)
-file, which stores tabular data in plain text.
+You can export issues from GitLab to a plain-text CSV
+([comma-separated values](https://en.wikipedia.org/wiki/Comma-separated_values))
+file. The CSV file is attached to an email, and sent to your default
+notification email address.
 
 <!-- vale gitlab.Spelling = NO -->
 
-CSV files can be used with any plotter or spreadsheet-based program, such as
-Microsoft Excel, Open Office Calc, or Google Sheets.
+CSV files can be used with any plotter or spreadsheet-based program, like
+Microsoft Excel, OpenOffice Calc, or Google Sheets. Use a CSV list of issues to:
 
 <!-- vale gitlab.Spelling = YES -->
 
-Here are some of the uses of exporting issues as CSV files:
-
-- Make a snapshot of issues for offline analysis or to communicate with other
-  teams who may not be in GitLab.
+- Create a snapshot of issues for offline analysis, or to share with other
+  teams who might not be in GitLab.
 - Create diagrams, graphs, and charts from the CSV data.
-- Present the data in any other format for auditing or sharing reasons.
-- Import the issues elsewhere to a system outside of GitLab.
-- Long-term issues' data analysis with multiple snapshots created along the
-  time.
+- Convert the data to other formats for auditing or sharing.
+- Import the issues to a system outside of GitLab.
+- Analyze long-term trends with multiple snapshots created over time.
 - Use the long-term data to gather relevant feedback given in the issues, and
   improve your product based on real metrics.
 
-## Choosing which issues to include
-
-After selecting a project, from the issues page you can narrow down which
-issues to export using the search bar, along with the All/Open/Closed tabs. All
-issues returned are exported, including those not shown on the first page.
+## Select issues to export
 
-![CSV export button](img/csv_export_button_v12_9.png)
+You can export issues from individual projects, but not groups.
 
-GitLab asks you to confirm the number of issues and email address for the
-export, after which the email is prepared.
+Prerequisites:
 
-![CSV export modal dialog](img/csv_export_modal.png)
+- You must have at least the Reporter role.
 
-## Sorting
+1. On the left sidebar, select **Search or go to** and find your project.
+1. Select **Plan > Issues**.
+1. Above the list of issues, select **Search or filter results...**.
+1. In the dropdown list that appears, select the attributes to filter by.
+   For more information about filter options, see
+   [Filter the list of issues](managing_issues.md#filter-the-list-of-issues).
+1. In the upper right, select **Actions** (**{ellipsis_v}**) **> Export as CSV**.
+1. In the dialog, verify that the email address is correct, then select **Export issues**.
 
-Exported issues are always sorted by `Title`.
+All matching issues are exported, including those not shown on the first page.
+The exported CSV does not contain attachments from issues.
 
 ## Format
 
-Data is encoded with a comma as the column delimiter, with `"` used to quote
-fields if needed, and newlines to separate rows. The first row contains the
-headers, which are listed in the following table along with a description of
-the values:
-
-| Column                                   | Description                                               |
-|------------------------------------------|-----------------------------------------------------------|
-| Title                                    | Issue `title`                                             |
-| Description                              | Issue `description`                                       |
-| Issue ID                                 | Issue `iid`                                               |
-| URL                                      | A link to the issue on GitLab                             |
-| State                                    | `Open` or `Closed`                                        |
-| Author                                   | Full name of the issue author                             |
-| Author Username                          | Username of the author, with the `@` symbol omitted       |
-| Assignee                                 | Full name of the issue assignee                           |
-| Assignee Username                        | Username of the author, with the `@` symbol omitted       |
-| Confidential                             | `Yes` or `No`                                             |
-| Locked                                   | `Yes` or `No`                                             |
-| Due Date                                 | Formatted as `YYYY-MM-DD`                                 |
-| Created At (UTC)                         | Formatted as `YYYY-MM-DD HH:MM:SS`                        |
-| Updated At (UTC)                         | Formatted as `YYYY-MM-DD HH:MM:SS`                        |
-| Milestone                                | Title of the issue milestone                              |
-| Weight                                   | Issue weight                                              |
-| Labels                                   | Title of any labels joined with a `,`                     |
-| Time Estimate                            | [Time estimate](../time_tracking.md#estimates) in seconds |
-| Time Spent                               | [Time spent](../time_tracking.md#time-spent) in seconds   |
-| [Epic](../../group/epics/index.md) ID    | ID of the parent epic, introduced in 12.7                 |
-| [Epic](../../group/epics/index.md) Title | Title of the parent epic, introduced in 12.7              |
-
-In GitLab 14.7 and earlier, the first two columns were `Issue ID` and `URL`,
-which [caused an issue](https://gitlab.com/gitlab-org/gitlab/-/issues/34769)
-when importing back into GitLab.
-
-## Limitations
-
-- Export Issues to CSV is not available at the Group's Issues List.
-- Issues are sent as an email attachment, with a 15 MB export limit to ensure
-  successful delivery across a range of email providers. If you reach the limit,
-  we suggest narrowing the search before export, perhaps by exporting open and
-  closed issues separately.
-- CSV files are plain text files. This means that the exported CSV file doesn't
-  contain any issue attachments.
+The CSV file has this format:
+
+- Sort is by title.
+- Columns are delimited with commas.
+- Fields are quoted with double quotes (`"`) if needed.
+- Newline characters separate rows.
+
+## Columns
+
+The following columns are included in the CSV file.
+
+| Column            | Description |
+|-------------------|-------------|
+| Title             | Issue `title` |
+| Description       | Issue `description` |
+| Issue ID          | Issue `iid` |
+| URL               | A link to the issue on GitLab |
+| State             | `Open` or `Closed` |
+| Author            | Full name of the issue author |
+| Author Username   | Username of the author, with the `@` symbol omitted |
+| Assignee          | Full name of the issue assignee |
+| Assignee Username | Username of the author, with the `@` symbol omitted |
+| Confidential      | `Yes` or `No` |
+| Locked            | `Yes` or `No` |
+| Due Date          | Formatted as `YYYY-MM-DD` |
+| Created At (UTC)  | Formatted as `YYYY-MM-DD HH:MM:SS` |
+| Updated At (UTC)  | Formatted as `YYYY-MM-DD HH:MM:SS` |
+| Milestone         | Title of the issue milestone |
+| Weight            | Issue weight |
+| Labels            | Labels, separated by commas |
+| Time Estimate     | [Time estimate](../time_tracking.md#estimates) in seconds |
+| Time Spent        | [Time spent](../time_tracking.md#time-spent) in seconds |
+| Epic ID           | ID of the parent epic |
+| Epic Title        | Title of the parent epic |
+
+## Troubleshooting
+
+When working with exported issues, you might encounter the following issues.
+
+### Column order
+
+In GitLab 14.7 and earlier, the first two columns in exported files were `Issue ID` and `URL`,
+which caused problems importing data back into GitLab. For more information, see
+[issue 34769](https://gitlab.com/gitlab-org/gitlab/-/issues/34769).
+
+### Size of export
+
+Issues are sent as an email attachment, with a 15 MB export limit to ensure
+successful delivery across a range of email providers. If you reach the limit,
+narrow your search before export. For example, consider exporting open and
+closed issues separately.