info:To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
redirect_to:'index.md'
remove_date:'2022-02-24'
---
# Issue Data and Actions **(FREE)**
This file was moved to [another location](index.md).
Please read through the [GitLab Issue Documentation](index.md) for an overview on GitLab Issues.
## Parts of an Issue
The image below illustrates what an issue may look like. Certain parts
look slightly different or are absent, depending on the GitLab version
and the user's permissions.
You can find all of an issue's information on one page.
The numbers in the image correspond to the following features:
results in a **Join Zoom meeting** button at the top of the issue, just under the header.
Read more how to [add or remove a zoom meeting](associate_zoom_meeting.md).
### Publish an issue **(ULTIMATE)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30906) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.1.
If a status page application is associated with the project, you can use the `/publish`[quick action](../quick_actions.md) to publish the issue. Refer to [GitLab Status Page](../../../operations/incident_management/status_page.md) for more information.
<!-- This redirect file can be deleted after <2022-02-24>. -->
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->
When you create a new issue, you are prompted to fill in the [data and fields of the issue](issue_data_and_actions.md),
as illustrated below. If you know the values you want to assign to an issue, you can use the
[Quick actions](../quick_actions.md) feature to input values.
When you create a new issue, you are prompted to enter the fields of the issue.
If you know the values you want to assign to an issue, you can use
[quick actions](../quick_actions.md) to enter them.
While creating an issue, you can associate it to an existing epic from current group by
selecting it using **Epic** dropdown.
...
...
@@ -142,7 +142,13 @@ Follow these examples to form your new issue URL with prefilled fields.
- For a new issue in the GitLab Community Edition project with a pre-filled title,
a pre-filled description, and the confidential flag set, the URL would be `https://gitlab.com/gitlab-org/gitlab-foss/-/issues/new?issue[title]=Validate%20new%20concept&issue[description]=Research%20idea&issue[confidential]=true`
## Bulk edit issues at the project level
## Edit an issue
You can edit an issue's title and description.
To edit an issue, select **Edit title and description** (**{pencil}**).
### Bulk edit issues at the project level
> - Assigning epic ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/210470) in GitLab 13.2.
> - Editing health status [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218395) in GitLab 13.2.
...
...
@@ -169,7 +175,7 @@ To update multiple project issues at the same time:
1. Select the appropriate fields and their values from the sidebar.
1. Click **Update all**.
## Bulk edit issues at the group level
### Bulk edit issues at the group level
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7249) in GitLab 12.1.
> - Assigning epic ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/210470) in GitLab 13.2.
...
...
@@ -232,15 +238,23 @@ end; nil
## Closing issues
When you decide that an issue is resolved, or no longer needed, you can close the issue
using the close button:
When you decide that an issue is resolved, or no longer needed, you can close the issue.
