Commit 1173ed14 authored by Job van der Voort's avatar Job van der Voort

Merge branch 'docs/overview-features-3-ee' into 'master'

Add use cases for issues-related EE features

Closes #2810

See merge request !2330
parents 05dbdaa6 4bcfb41a
# CSV Export # Export Issues to CSV
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1126) in [GitLab Enterprise Edition Starter](https://about.gitlab.com/products/) 9.0. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1126) in [GitLab Enterprise Edition Starter 9.0](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#export-issues-ees-eep).
Issues can be exported as CSV from GitLab and are sent to your default notification email as an attachment. Issues can be exported as CSV from GitLab and are sent to your default notification email as an attachment.
## Overview
**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.
> _CSVs are a handy way of getting data from one program to another where one program cannot read the other ones normal output._ [Ref](https://www.quora.com/What-is-a-CSV-file-and-its-uses)
CSV files can be used with any plotter or spreadsheet-based program, such as Microsoft Excel,
Open Office Calc, or Google Spreadsheets.
## Use cases
Among numerous use cases for exporting issues for CSV, we can name a few:
- Make a snapshot of issues for offline analysis or to communicate with other teams who may 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
- Long-term issues' data analysis with multiple snapshots created along the 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 ## Choosing which issues to include
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 will be exported, including those not shown on the first page. 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 will be exported, including those not shown on the first page.
......
...@@ -5,13 +5,13 @@ for tracking the evolution of a new idea or the process ...@@ -5,13 +5,13 @@ for tracking the evolution of a new idea or the process
of solving a problem. of solving a problem.
It allows you, your team, and your collaborators to share It allows you, your team, and your collaborators to share
and discuss proposals, before and while implementing them. and discuss proposals before and while implementing them.
Issues and the GitLab Issue Tracker are available in all Issues and the GitLab Issue Tracker are available in all
[GitLab Products](https://about.gitlab.com/products/) as [GitLab Products](https://about.gitlab.com/products/) as
part of the [GitLab Workflow](https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/). part of the [GitLab Workflow](https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/).
## Use-Cases ## Use cases
Issues can have endless applications. Just to exemplify, these are Issues can have endless applications. Just to exemplify, these are
some cases for which creating issues are most used: some cases for which creating issues are most used:
...@@ -23,7 +23,28 @@ some cases for which creating issues are most used: ...@@ -23,7 +23,28 @@ some cases for which creating issues are most used:
- Obtaining support - Obtaining support
- Elaborating new code implementations - Elaborating new code implementations
See also the blog post [Always start a discussion with an issue](https://about.gitlab.com/2016/03/03/start-with-an-issue/). See also the blog post "[Always start a discussion with an issue](https://about.gitlab.com/2016/03/03/start-with-an-issue/)".
### Keep private things private
For instance, let's assume you have a public project but want to start a discussion on something
you don't want to be public. With [Confidential Issues](#confidential-issues),
you can discuss private matters among the project members, and still keep
your project public, open to collaboration.
### Streamline collaboration
With [Multiple Assignees for Issues](multiple_assignees_for_issues.md),
available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/)
you can streamline collaboration and allow shared responsibilities to be clearly displayed.
All assignees are shown across your workflows and receive notifications (as they
would as single assignees), simplifying communication and ownership.
### Consistent collaboration
Create [issue templates](#issue-templates) to make collaboration consistent and
containing all information you need. For example, you can create a template
for feature proposals and another one for bug reports.
## Issue Tracker ## Issue Tracker
...@@ -102,8 +123,14 @@ Multiple Issue Boards enables you to create more than one Issue Board per projec ...@@ -102,8 +123,14 @@ Multiple Issue Boards enables you to create more than one Issue Board per projec
It's great for large projects with more than one team or in situations where a It's great for large projects with more than one team or in situations where a
repository is used to host the code of multiple products. repository is used to host the code of multiple products.
[Multiple Issue Boards](../issue_board.html#multiple-issue-boards) _[Multiple Issue Boards](../issue_board.html#multiple-issue-boards)
are available only in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/). are available only in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/)._
### Export Issues to CSV (EES/EEP)
Issues can be [exported as CSV](csv_export.md) from GitLab and are sent to your email as an attachment.
_Exporting issues to CSV is available only in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/)._
### Issue's API ### Issue's API
......
...@@ -43,8 +43,6 @@ assigned to them if they created the issue themselves. ...@@ -43,8 +43,6 @@ assigned to them if they created the issue themselves.
##### 3.1. Multiple Assignees (EES/EEP) ##### 3.1. Multiple Assignees (EES/EEP)
Issue Weights are only available in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/).
Often multiple people likely work on the same issue together, Often multiple people likely work on the same issue together,
which can especially be difficult to track in large teams which can especially be difficult to track in large teams
where there is shared ownership of an issue. where there is shared ownership of an issue.
...@@ -52,9 +50,7 @@ where there is shared ownership of an issue. ...@@ -52,9 +50,7 @@ where there is shared ownership of an issue.
In GitLab Enterprise Edition, you can also select multiple assignees In GitLab Enterprise Edition, you can also select multiple assignees
to an issue. to an issue.
> **Note:** Learn more on the [Multiple Assignees documentation](multiple_assignees_for_issues.md).
Multiple Assignees was [introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1904)
in [GitLab Enterprise Edition 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
#### 4. Milestone #### 4. Milestone
......
# Multiple Assignees for Issues
> **Note:**
[Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1904)
in [GitLab Enterprise Edition Starter 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
## Overview
In large teams, where there is shared ownership of an issue, it can be difficult
to track who is working on it, who already completed their contributions, who
didn't even start yet.
In [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/),
you can also select multiple assignees to an issue, making it easier to
track, and making clearer who is accountable for it.
![multiple assignees for issues](img/multiple_assignees_for_issues.png)
## Use cases
Consider a team formed by frontend developers, backend developers,
UX designers, QA testers, and a product manager working together to bring an idea to
market.
Multiple Assignees for Issues makes collaboration smother,
and allows shared responsibilities to be clearly displayed.
All assignees are shown across your team's workflows and receive notifications (as they
would as single assignees), simplifying communication and ownership.
Once an assignee had their work completed, they would remove themselves as assignees, making
it clear that their role is complete.
## How it works
From an opened issue, expand the right sidebar, locate the assignees entry,
and click on **Edit**. From the dropdown menu, select as many users as you want
to assign the issue to.
![adding multiple assignees](img/multiple_assignees.gif)
An assignee can be easily removed by deselecting them from the same dropdown menu.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment