Make screenshots in images/help/projects-v2 accessable (#36506)
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
|
Before Width: | Height: | Size: 96 KiB After Width: | Height: | Size: 62 KiB |
|
Before Width: | Height: | Size: 96 KiB After Width: | Height: | Size: 62 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 60 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 50 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 71 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 62 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 64 KiB |
BIN
assets/images/help/projects-v2/copy-project-form.png
Normal file
|
After Width: | Height: | Size: 98 KiB |
|
Before Width: | Height: | Size: 6.9 KiB After Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 26 KiB |
BIN
assets/images/help/projects-v2/hidden-items.png
Normal file
|
After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 5.0 KiB After Width: | Height: | Size: 2.3 KiB |
BIN
assets/images/help/projects-v2/issue-create-form.png
Normal file
|
After Width: | Height: | Size: 76 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 7.7 KiB |
|
Before Width: | Height: | Size: 6.2 KiB After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 9.6 KiB After Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 7.9 KiB After Width: | Height: | Size: 12 KiB |
BIN
assets/images/help/projects-v2/migrate-option.png
Normal file
|
After Width: | Height: | Size: 295 KiB |
|
Before Width: | Height: | Size: 4.6 KiB After Width: | Height: | Size: 3.2 KiB |
|
Before Width: | Height: | Size: 7.9 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 7.5 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 9.8 KiB After Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 2.4 KiB |
BIN
assets/images/help/projects-v2/projects-classic-org.png
Normal file
|
After Width: | Height: | Size: 34 KiB |
BIN
assets/images/help/projects-v2/projects-profile-menu.png
Normal file
|
After Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 390 KiB |
|
Before Width: | Height: | Size: 8.3 KiB After Width: | Height: | Size: 9.1 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 35 KiB |
|
Before Width: | Height: | Size: 6.9 KiB After Width: | Height: | Size: 9.8 KiB |
|
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 9.6 KiB |
|
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 8.9 KiB |
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 6.3 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 9.0 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 9.6 KiB |
@@ -19,26 +19,15 @@ When you copy a project, the new project will contain the same views and custom
|
||||
## Copying an existing project
|
||||
|
||||
1. Navigate to the project you want to copy.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %} to open the menu.
|
||||
|
||||

|
||||

|
||||
|
||||
1. In the menu, click {% octicon "copy" aria-label="The copy icon" %} **Make a copy**.
|
||||
1. In the menu, click {% octicon "copy" aria-hidden="true" %} **Make a copy**.
|
||||
1. Optionally, if you want all draft issues to be copied with the project, in the "Make a copy" dialog, select **Draft issues will be copied if selected**.
|
||||
|
||||

|
||||
|
||||
1. Optionally, if you want all draft issues to be copied with the project, select **Include draft issues**.
|
||||
|
||||

|
||||
|
||||
1. In the dialog, under "Owner", select either the organization that will own the new project or your personal account.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Under "Owner", select either the organization that will own the new project or your personal account.
|
||||
1. Under "New project name", type the name of the new project.
|
||||
|
||||

|
||||
|
||||
1. Click **Copy project**.
|
||||
|
||||

|
||||
|
||||
@@ -40,7 +40,10 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. In the top right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your projects**.
|
||||
|
||||

|
||||
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||

|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
@@ -57,6 +60,7 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||

|
||||

|
||||
|
||||
1. In the left sidebar, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -40,7 +40,6 @@ You can set each view in your project to a different layout.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Under "Layout", click either **Table**{% ifversion projects-v2-roadmaps %}, **Board** or **Roadmap**{% else %} or **Board**{% endif %}.
|
||||
{% ifversion projects-v2-roadmaps %}{% else %}{% endif %}
|
||||
|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout."
|
||||
|
||||
@@ -24,10 +24,8 @@ For more information about changing a view to use the board layout, see "[AUTOTI
|
||||
In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**.
|
||||

|
||||
1. Click {% octicon "columns" aria-hidden="true" %} **Column field**.
|
||||
1. Click the field you want to use.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by."
|
||||
|
||||
@@ -37,14 +35,11 @@ Alternatively, open the project command palette by pressing {% data variables.pr
|
||||
|
||||
In the board layout, you can can choose which columns to display. The available columns are made up of the contents of your selected column field.
|
||||
|
||||
1. In the board layout, scroll to the right of your columns, and click {% octicon "plus" aria-label="the plus icon" %}.
|
||||
1. In the board layout, scroll to the right of your columns, and click {% octicon "plus" aria-label="Add a new column to the board" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Select the columns you want to show.
|
||||
|
||||

|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion projects-v2-consistent-sorting %}
|
||||
|
||||
@@ -19,19 +19,13 @@ For more information about changing a view to use the roadmap layout, see "[AUTO
|
||||
|
||||
You can set the date or iteration fields that your roadmap will use to position items. When you set a view to a roadmap layout, {% data variables.product.company_short %} will attempt to use existing date and iteration fields you have already set up. For more information on creating new fields, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields)."
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "calendar" aria-label="the calendar icon" %} **Date fields**.
|
||||
1. In the top right of your roadmap, click {% octicon "calendar" aria-hidden="true" %} **Date fields**.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-label="the plus icon" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
|
||||

|
||||
|
||||
1. Select a date or iteration field for "Start date" and "Target date."
|
||||
|
||||

|
||||
|
||||
|
||||
{% ifversion projects-v2-roadmap-markers %}
|
||||
|
||||
## Setting vertical markers
|
||||
@@ -50,14 +44,12 @@ You can configure vertical markers on a roadmap to show your iterations, the dat
|
||||
|
||||
You can choose the density of items on your roadmap. You can zoom in to show one month at a time or, for a greater overview, you can zoom out to show a quarter of a year or a full year.
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "search" aria-label="the zoom icon" %}.
|
||||
1. In the top right of your roadmap, click {% octicon "search" aria-label="The zoom icon next to Month, Quarter, or Year" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Select either **Month**, **Quarter**, or **Year**.
|
||||
|
||||

|
||||
|
||||
{% ifversion projects-v2-consistent-sorting %}
|
||||
|
||||
## Sorting by field values
|
||||
|
||||
@@ -23,10 +23,9 @@ You can show or hide a specific field.
|
||||
|
||||
You can also hide individual fields using the field headers.
|
||||
|
||||
1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}.
|
||||

|
||||
1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**.
|
||||

|
||||
1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="Status column options" %}.
|
||||

|
||||
1. Click {% octicon "eye-closed" aria-hidden="true" %} **Hide field**.
|
||||
|
||||
## Grouping by field values
|
||||
|
||||
@@ -39,7 +38,9 @@ You can group items by a custom field value. When items are grouped, if you drag
|
||||
You can change the order of fields.
|
||||
|
||||
1. Click the field header.
|
||||

|
||||
|
||||

|
||||
|
||||
2. While continuing to click, drag the field to the required location.
|
||||
|
||||
## Reordering rows
|
||||
@@ -47,7 +48,9 @@ You can change the order of fields.
|
||||
You can change the order of rows.
|
||||
|
||||
1. Click the number at the start of the row.
|
||||

|
||||
|
||||

|
||||
|
||||
2. While continuing to click, drag the row to the required location.
|
||||
|
||||
## Sorting by field values
|
||||
|
||||
@@ -13,7 +13,7 @@ allowTitleToDifferFromFilename: true
|
||||
|
||||
You can customize which items appear in your views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
|
||||
|
||||
To filter a view, click {% octicon "filter" aria-label="The Filter icon" %} and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the project command palette, by pressing {% data variables.projects.command-palette-shortcut %}, and type "Filter by" to choose from the available filters.
|
||||
To filter a view, click {% octicon "filter" aria-label="Filter by keyword or by field" %} and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the project command palette, by pressing {% data variables.projects.command-palette-shortcut %}, and type "Filter by" to choose from the available filters.
|
||||
|
||||

|
||||
|
||||
|
||||
@@ -32,8 +32,7 @@ You can duplicate an existing view and use it as a base to make further changes.
|
||||
|
||||
1. Switch to the view you want to duplicate.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "versions" aria-label="the versions icon" %} **Duplicate view**.
|
||||

|
||||
1. Click {% octicon "versions" aria-hidden="true" %} **Duplicate view**.
|
||||
|
||||
## Saving changes to a view
|
||||
|
||||
@@ -57,8 +56,7 @@ You can rename your saved views. The name change is automatically saved.
|
||||
|
||||
1. Switch to the view you want to rename.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**.
|
||||

|
||||
1. Click {% octicon "pencil" aria-hidden="true" %} **Rename view**.
|
||||
1. Type the new name for your view.
|
||||
1. To save your changes, press <kbd>Return</kbd>.
|
||||
|
||||
@@ -66,7 +64,6 @@ You can rename your saved views. The name change is automatically saved.
|
||||
|
||||
1. Switch to the view you want to delete.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "trash" aria-label="the trasj icon" %} **Delete view**.
|
||||

|
||||
1. Click {% octicon "trash" aria-hidden="true" %} **Delete view**.
|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Delete view."
|
||||
|
||||
@@ -59,11 +59,8 @@ Next, create an iteration field so you can plan and track your work over repeati
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Iteration**
|
||||

|
||||
3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
|
||||

|
||||
4. Click **Save**.
|
||||

|
||||
|
||||
## Creating a field to track priority
|
||||
|
||||
@@ -71,12 +68,9 @@ Now, create a custom field named `Priority` and containing the values: `High`, `
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Single select**
|
||||

|
||||
1. Below "Options", type the first option, "High".
|
||||

|
||||
1. To add additional fields, for "Medium" and "Low", click **Add option**.
|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
Specify a priority for all issues in your project.
|
||||
|
||||
@@ -88,9 +82,7 @@ Next, group all of the items in your project by priority to make it easier to fo
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**.
|
||||

|
||||
1. Click **Priority**.
|
||||

|
||||
|
||||
Now, move issues between groups to change their priority.
|
||||
|
||||
@@ -125,7 +117,6 @@ Next, switch to board layout.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Under "Layout", click **Board**.
|
||||

|
||||
|
||||

|
||||
|
||||
@@ -137,7 +128,6 @@ To indicate the purpose of the view, give it a descriptive name.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**.
|
||||

|
||||
1. Type the new name for your view.
|
||||
1. To save changes, press <kbd>Return</kbd>.
|
||||
|
||||
@@ -153,41 +143,25 @@ Next, configure the auto-add workflow to automatically add issues opened in a re
|
||||
|
||||
{% data reusables.projects.access-workflows %}
|
||||
1. In the "Default workflows" list, click **Auto-add to project**.
|
||||
|
||||

|
||||
|
||||
1. To start editing the workflow, in the top right, click **Edit**.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Under "Filters", select the repository you want to add items from.
|
||||
|
||||

|
||||
|
||||
1. Next to the repository selection, type the filter criteria you want items to match before they are automatically added to your project. For example, to catch all issues and PRs opened with the label "bug", use `is:issue,pr label:bug`.
|
||||
|
||||

|
||||
|
||||
1. To enable the new workflow, click **Save and turn on workflow**.
|
||||
|
||||

|
||||
|
||||
{% endif %}
|
||||
|
||||
Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
|
||||
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||

|
||||

|
||||
1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
|
||||

|
||||
1. Under **Default workflows**, click **Item added to project**.
|
||||

|
||||
1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
|
||||

|
||||
1. Next to **Set**, select **Status:Todo**.
|
||||

|
||||
1. Click the **Disabled** toggle to enable the workflow.
|
||||

|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -57,20 +57,17 @@ You can copy the URL of an issue or pull request into your clipboard and paste t
|
||||
If you know the issue or pull request number or if you know part of the title, you can search for an issue or pull request directly from your project.
|
||||
|
||||
{% data reusables.projects.add-item-bottom-row %}
|
||||
2. Enter <kbd>#</kbd>.
|
||||
2. To open the list of repositories, type <kbd>#</kbd>.
|
||||
3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
|
||||

|
||||
4. Select the issue or pull request. You can type part of the title to narrow down your options.
|
||||

|
||||
|
||||
### Bulk adding issues and pull requests
|
||||
|
||||
You can add multiple issues and pull requests from your project and use filters, such as `label:bug`, to narrow down your search.
|
||||
|
||||
1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}.
|
||||

|
||||
1. In the bottom row of the project, click {% octicon "plus" aria-hidden="true" %}.
|
||||

|
||||
1. Click **Add item from repository**.
|
||||
{% ifversion projects-v2-create-issue-modal %}{% else %}{% endif %}
|
||||
{% data reusables.projects.bulk-add %}
|
||||
|
||||
### Adding multiple issues or pull requests from a repository
|
||||
@@ -88,9 +85,7 @@ You can also add issues and pull requests to your project from a repository's is
|
||||
|
||||

|
||||
1. Above the list of issues or pull requests, click **Projects**.
|
||||

|
||||
1. Click the projects you want to add the selected issues or pull requests to.
|
||||

|
||||
|
||||
### Assigning a project from within an issue or pull request
|
||||
|
||||
@@ -98,11 +93,9 @@ You can also add an issue or pull request to your project from within the issue
|
||||
|
||||
1. Navigate to the issue or pull request that you want to add to a project.
|
||||
2. In the side bar, click **Projects**.
|
||||

|
||||

|
||||
3. Select the project that you want to add the issue or pull request to.
|
||||

|
||||
4. Optionally, populate the custom fields.
|
||||

|
||||
|
||||
### Using the command palette to add an issue or pull request
|
||||
|
||||
|
||||
@@ -10,6 +10,13 @@ topics:
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
## Archiving items
|
||||
|
||||
You can archive an item to keep the context about the item in the project but remove it from the project views. {% ifversion projects-v2-auto-archive %}You can also configure your project's built-in workflows to automatically archive items that meet certain criteria. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %}
|
||||
@@ -17,16 +24,15 @@ You can archive an item to keep the context about the item in the project but re
|
||||
{% data reusables.projects.select-an-item %}
|
||||
{% data reusables.projects.open-item-menu %}
|
||||
1. Click **Archive**.
|
||||

|
||||
1. When prompted, confirm your choice by clicking **Archive**.
|
||||

|
||||
|
||||
## Restoring archived items
|
||||
|
||||
1. Navigate to your project.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. In the menu, click {% octicon "archive" aria-hidden="true" %} **Archived items**.
|
||||
1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
|
||||
1. To the left of each item title, select the items you would like to restore.
|
||||
@@ -41,6 +47,4 @@ You can delete an item to remove it from the project entirely.
|
||||
{% data reusables.projects.select-an-item %}
|
||||
{% data reusables.projects.open-item-menu %}
|
||||
1. Click **Delete from project**.
|
||||

|
||||
1. When prompted, confirm your choice by clicking **Delete**.
|
||||

|
||||
|
||||
@@ -11,21 +11,21 @@ topics:
|
||||
|
||||
## Converting draft issues in table layout
|
||||
|
||||
1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert.
|
||||

|
||||
1. Click the {% octicon "triangle-down" aria-label="Row actions" %} on the draft issue that you want to convert.
|
||||
|
||||

|
||||
|
||||
2. Select **Convert to issue**.
|
||||

|
||||
3. Select the repository that you want to add the issue to.
|
||||

|
||||
|
||||
## Converting draft issues in board layout
|
||||
|
||||
1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert.
|
||||
|
||||

|
||||
|
||||
2. Select **Convert to issue**.
|
||||

|
||||
3. Select the repository that you want to add the issue to.
|
||||

|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -16,10 +16,7 @@ In order for repository members to see a project listed in a repository, they mu
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-label="the project icon" %} **Projects**.
|
||||

|
||||

|
||||
1. Click **Add project**.
|
||||

|
||||
1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
|
||||

|
||||
1. Click on a project to list it in your repository.
|
||||

|
||||
|
||||
@@ -39,13 +39,8 @@ Teams are granted read permissions on any project they are added to. This permis
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||
|
||||

|
||||
|
||||
1. Next to the team that you want to remove from the project, click **Remove**.
|
||||
|
||||

|
||||
|
||||
|
||||
{% ifversion projects-v1 %}
|
||||
|
||||
|
||||
@@ -29,9 +29,10 @@ The default base role is `write`, meaning that everyone in the organization can
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||

|
||||
2. Under **Base role**, select the default role.
|
||||

|
||||
|
||||

|
||||
|
||||
- **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
|
||||
- **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
|
||||
- **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
|
||||
@@ -51,31 +52,28 @@ You can only invite an individual user to collaborate on your organization-level
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||

|
||||
2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
|
||||
|
||||

|
||||
|
||||
3. Select the role for the collaborator.
|
||||

|
||||
- **Read**: The team or individual can view the project.
|
||||
- **Write**: The team or individual can view and edit the project.
|
||||
- **Admin**: The team or individual can view, edit, and add new collaborators to the project.
|
||||
4. Click **Invite**.
|
||||

|
||||
|
||||
### Managing access of an existing collaborator on your project
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||

|
||||
1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
|
||||
|
||||
You can use the **Type** and **Role** drop-down menus to filter the access list.
|
||||
|
||||

|
||||
|
||||
1. Edit the role for the collaborator(s).
|
||||

|
||||
1. Optionally, click **Remove** to remove the collaborator(s).
|
||||

|
||||
|
||||
## Managing access for user-level projects
|
||||
|
||||
@@ -89,28 +87,25 @@ This only affects collaborators for your project, not for repositories in your p
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||

|
||||
2. Under **Invite collaborators**, search for the user that you want to invite.
|
||||
|
||||

|
||||
|
||||
3. Select the role for the collaborator.
|
||||

|
||||
- **Read**: The individual can view the project.
|
||||
- **Write**: The individual can view and edit the project.
|
||||
- **Admin**: The individual can view, edit, and add new collaborators to the project.
|
||||
4. Click **Invite**.
|
||||

|
||||
|
||||
### Managing access of an existing collaborator on your project
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||

|
||||
1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
|
||||
|
||||
You can use the **Type** and **Role** drop-down menus to filter the access list.
|
||||

|
||||
|
||||

|
||||
|
||||
1. Edit the role for the collaborator(s).
|
||||

|
||||
1. Optionally, click **Remove** to remove the collaborator(s).
|
||||

|
||||
|
||||
@@ -19,7 +19,7 @@ Projects can be public or private. For public projects, everyone on the internet
|
||||
|
||||
Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository.
|
||||
|
||||

|
||||

|
||||
|
||||
Project admins and organization owners can control project visibility. Organization owners{% ifversion project-visibility-policy %} and enterprise owners{% endif %} can restrict the ability to change project visibility to just organization owners.
|
||||
|
||||
@@ -33,7 +33,6 @@ Project admins can also manage write and admin access to their project and contr
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**.
|
||||

|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -23,8 +23,6 @@ If your project makes use of date fields, you can use the roadmap layout to view
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Date**
|
||||

|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
|
||||
|
||||
@@ -27,14 +27,10 @@ If your project makes use of iteration fields, you can use the roadmap layout to
|
||||
## Adding an iteration field
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Iteration**
|
||||

|
||||
1. Under "Field type", select **Iteration**.
|
||||
2. Optionally, if you don't want the iteration to start today, select the calendar dropdown next to "Starts on" and choose a new start date.
|
||||

|
||||
3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
|
||||

|
||||
4. Click **Save**.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
|
||||
|
||||
@@ -42,29 +38,24 @@ Alternatively, open the project command palette by pressing {% data variables.pr
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the iteration field you want to adjust.
|
||||

|
||||
1. To add a new iteration of the same duration, click **Add iteration**.
|
||||

|
||||
1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} **More options**, select a starting date and duration, and click **Add**.
|
||||

|
||||

|
||||
1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-hidden="true" %} **More options**, select a starting date and duration, and click **Add**.
|
||||

|
||||
1. Click **Save changes**.
|
||||

|
||||
|
||||
## Editing an iteration
|
||||
|
||||
You can edit iterations in your project settings. You can also access the settings for an iteration field by clicking {% octicon "triangle-down" aria-label="The triangle icon" %} in the table header for the field and clicking **Edit values**.
|
||||
You can edit iterations in your project settings. You can also access the settings for an iteration field by clicking {% octicon "kebab-horizontal" aria-label="Cycle column options" %} in the table header for the field and clicking **Edit values**.
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the iteration field you want to adjust.
|
||||

|
||||
1. In the list on the left, click the name of the iteration field you want to adjust.
|
||||
1. To change the name of an iteration, click on the name and start typing.
|
||||

|
||||

|
||||
1. To change the date or duration of an iteration, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
|
||||

|
||||
1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||

|
||||

|
||||
1. Optionally, to delete an iteration, on the right of the iteration, click {% octicon "trash" aria-label="Remove item" %}.
|
||||
2. Click **Save changes**.
|
||||

|
||||
|
||||
## Inserting a break
|
||||
|
||||
@@ -72,10 +63,8 @@ You can insert breaks into your iterations to communicate when you are taking ti
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the iteration field you want to adjust.
|
||||

|
||||
2. Hover over the dividing line above an iteration, then click **Insert break**.
|
||||
|
||||

|
||||
3. Optionally, to change the duration of the break, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
|
||||
4. Click **Save changes**.
|
||||

|
||||
|
||||
@@ -19,12 +19,9 @@ Single select fields can contain up to 50 options.
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Single select**
|
||||

|
||||
1. Below "Options", type the first option.
|
||||

|
||||
- To add additional options, click **Add option**.
|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
|
||||
|
||||
@@ -52,12 +49,8 @@ You can set descriptions and colors for each of your single select options.
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the single select field you want to adjust.
|
||||

|
||||
1. Edit existing options or click **Add option**.
|
||||

|
||||
1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}.
|
||||

|
||||
1. Optionally, to delete an option, click {% octicon "x" aria-label="Remove option" %}.
|
||||
1. Click **Save options**.
|
||||

|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -20,19 +20,15 @@ Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and
|
||||
## Adding a text field
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Text**
|
||||

|
||||
1. Select **Text**.
|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
|
||||
|
||||
## Adding a number field
|
||||
|
||||
{% data reusables.projects.new-field %}
|
||||
1. Select **Number**
|
||||

|
||||
1. Select **Number**.
|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field."
|
||||
|
||||
@@ -29,12 +29,10 @@ You can enable the Tracked by field to see which issues are tracking an item in
|
||||
|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Under "Hidden fields", click **Tracked by**.
|
||||
|
||||

|
||||
|
||||
|
||||
## Enabling the Tracks field
|
||||
|
||||
@@ -42,8 +40,6 @@ You can enable the Tracks field to see what other issues an item in your project
|
||||
|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Under "Hidden fields", click **Tracks**.
|
||||
|
||||

|
||||
|
||||
@@ -12,8 +12,6 @@ redirect_from:
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the custom field you want to delete.
|
||||

|
||||
1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||

|
||||
1. Click **Delete field**.
|
||||

|
||||
|
||||

|
||||
|
||||
@@ -12,7 +12,5 @@ redirect_from:
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click the name of the custom field you want to rename.
|
||||

|
||||
1. Under "Field name", type the new name for the field.
|
||||

|
||||
1. To save changes, press <kbd>Return</kbd>.
|
||||
|
||||
@@ -14,16 +14,9 @@ topics:
|
||||
|
||||
{% data reusables.projects.access-insights %}
|
||||
1. In the menu on the left, click on the chart you would like to configure.
|
||||

|
||||
1. On the right side of the page, click **Configure**. A panel will open on the right.
|
||||

|
||||
1. To change the type of chart, select the **Layout** dropdown and click on the chart type you want to use.
|
||||

|
||||
1. To change the field used for your chart's X-axis, select the **X-axis** dropdown and click the field you want to use.
|
||||

|
||||
1. Optionally, to group the items on your X-axis by another field, select **Group by** and click on the field you want to use, or click "None" to disable grouping.
|
||||

|
||||
1. Optionally, if your project contains number fields and you want the Y-axis to display the sum, average, minimum, or maximum of one of those number fields, select **Y-axis** and click an option. Then, select the dropdown that appears beneath and click on the number field you want to use.
|
||||

|
||||
1. To save your chart, click **Save changes**.
|
||||

|
||||
|
||||
@@ -14,9 +14,6 @@ topics:
|
||||
|
||||
{% data reusables.projects.access-insights %}
|
||||
3. In the menu on the left, click **New chart**.
|
||||

|
||||
4. Optionally, to change the name of the new chart, click {% octicon "triangle-down" aria-label="The triangle icon" %}, type a new name, and press <kbd>Return</kbd>.
|
||||

|
||||
5. Above the chart, type filters to change the data used to build the chart. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
|
||||
6. To the right of the filter text box, click **Save changes**.
|
||||

|
||||
|
||||
@@ -27,7 +27,6 @@ This option may not be available to you if an enterprise owner restricts visibil
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
|
||||
1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**.
|
||||

|
||||
1. Click **Save**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -15,12 +15,9 @@ After you disable insights for projects in your organization, it won't be possib
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**.
|
||||

|
||||
1. In the sidebar, click **{% octicon "sliders" aria-hidden="true" %} Features**.
|
||||
1. Under "Insights", deselect **Enable Insights for the organization**.
|
||||

|
||||
1. Click **Save**.
|
||||

|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Click **New Project**.
|
||||
|
||||

|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. Navigate to your project.
|
||||
2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}.
|
||||

|
||||
2. In the top-right, to access insights, click {% octicon "graph" aria-label="Navigate to insights" %}.
|
||||

|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
1. Navigate to your project.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||
|
||||

|
||||

|
||||
|
||||
1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
{% data reusables.projects.add-item-bottom-row %}
|
||||
1. Type your idea, then press **Enter**.
|
||||

|
||||
1. To add body text, click on the title of the draft issue. In the markdown input box that appears, enter the text for the draft issue body, then click **Save**.
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
|
||||

|
||||
1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="Create new item or add existing item" %}.
|
||||

|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
{% data reusables.projects.add-item-bottom-row %}
|
||||
1. Paste the URL of the issue or pull request.
|
||||

|
||||
3. To add the issue or pull request, press <kbd>Return</kbd>.
|
||||
|
||||
@@ -1,6 +1,4 @@
|
||||
1. Optionally, to change the repository, click the dropdown and select a repository. You can also search for specific issues and pull requests.
|
||||

|
||||

|
||||
1. Select the issues and pull requests you want to add.
|
||||

|
||||
1. Click **Add selected items**.
|
||||

|
||||
|
||||
@@ -1,31 +1,19 @@
|
||||
1. At the bottom of a table, group of items, or a column in board layout, click {% octicon "plus" aria-label="plus icon" %}.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Click **Create new issue**.
|
||||
|
||||

|
||||
|
||||
1. At the top of the "Create new issue" dialog, select the repository where you want the new issue to be created.
|
||||
|
||||

|
||||

|
||||
|
||||
1. Below the repository dropdown, type a title for the new issue.
|
||||
|
||||

|
||||
|
||||
1. Optionally, use the fields below the title field to set assignees, labels, and milestones, and add the new issue to other projects.
|
||||
|
||||

|
||||
|
||||
1. Optionally, type a description for your issue.
|
||||
|
||||

|
||||
|
||||
1. Optionally, if you want to create more issues, select **Create more** and the dialog will reopen when you create your issue.
|
||||
|
||||

|
||||
|
||||
1. Click **Create**.
|
||||
|
||||

|
||||
|
||||
@@ -3,5 +3,9 @@
|
||||
1. Under your organization name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||

|
||||
1. Click **New project**.
|
||||

|
||||
1. In the left sidebar, click a format or template, then click **Create**.
|
||||
1. Optionally, in the text box under "Project name", type a name for your new project.
|
||||
|
||||

|
||||
|
||||
1. Click a template or, to start with an empty project, click **Table** or **Board**.
|
||||
1. Click **Create**.
|
||||
|
||||
@@ -1,6 +1,12 @@
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On your profile, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||

|
||||
|
||||

|
||||
|
||||
1. Click **New project**.
|
||||

|
||||
1. In the left sidebar, click a format or template, then click **Create**.
|
||||
1. Optionally, in the text box under "Project name", type a name for your new project.
|
||||
|
||||

|
||||
|
||||
1. Click a template or, to start with an empty project, click **Table** or **Board**.
|
||||
1. Click **Create**.
|
||||
|
||||
@@ -5,11 +5,8 @@
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**.
|
||||

|
||||
1. Click {% octicon "rows" aria-hidden="true" %} **Group**.
|
||||
1. Click the field you want to group by.
|
||||

|
||||
2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list.
|
||||

|
||||
1. Optionally, to disable grouping, click {% octicon "x" aria-hidden="true" %} **No grouping** at the bottom of the list.
|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by."
|
||||
|
||||
@@ -1,7 +1,5 @@
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields.
|
||||

|
||||
1. Under "Configuration", click {% octicon "note" aria-hidden="true" %} **Fields**.
|
||||
1. Select or deselect the fields you want to show or hide.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field.
|
||||
|
||||
@@ -1,11 +1,10 @@
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click **Sort**.
|
||||

|
||||
1. Click the field you want to sort by.
|
||||

|
||||
1. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}.
|
||||

|
||||
1. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-hidden="true" %}.
|
||||
|
||||

|
||||
|
||||
1. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list.
|
||||

|
||||
|
||||
Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by."
|
||||
|
||||
@@ -4,9 +4,4 @@ In a board layout, field sums are displayed at the top of each column. In table{
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "number" aria-label="the number icon" %} **Field sum**.
|
||||
|
||||

|
||||
|
||||
1. Select the fields you want to include.
|
||||
|
||||

|
||||
|
||||
@@ -18,7 +18,4 @@
|
||||
1. Next to "Set", choose the value that you want to set the status to.
|
||||
1. If the workflow is disabled, click the toggle next to "Off" to enable the workflow.
|
||||
|
||||

|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,4 @@
|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
|
||||

|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="Add field" %}.
|
||||

|
||||
1. Click **New field**.
|
||||

|
||||
1. Type the name of your new field.
|
||||

|
||||
1. At the top of the dropdown, type the name of your new field.
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. To the right of your existing views, click **New view**
|
||||

|
||||

|
||||
|
||||
@@ -1 +1 @@
|
||||
1. Select the {% octicon "triangle-down" aria-label="the item menu" %} (in table{% ifversion projects-v2-roadmaps %} or roadmap{% endif %} layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout).
|
||||
1. Click {% octicon "triangle-down" aria-label="Row actions" %} (in table{% ifversion projects-v2-roadmaps %} or roadmap{% endif %} layout) or {% octicon "kebab-horizontal" aria-hidden="true" %} (in board layout).
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the name of the currently open view.
|
||||

|
||||
1. Click {% octicon "triangle-down" aria-label="View options" %} next to the name of the currently open view.
|
||||

|
||||
|
||||
@@ -2,12 +2,9 @@ You can set your project's description and README to share the purpose of your p
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. To add a short description to your project, under "Add a description", type your description in the text box and click **Save**.
|
||||

|
||||
1. To update your project's README, under "README", type your content in the text box.
|
||||
- You can format your README using Markdown. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
|
||||
- To toggle between the text box and a preview of your changes, click {% octicon "eye" aria-label="The preview icon" %} or {% octicon "pencil" aria-label="The edit icon" %}.
|
||||

|
||||
1. To save changes to your README, click **Save**.
|
||||

|
||||
|
||||
You can view and make quick changes to your project description and README by navigating to your project and clicking {% octicon "sidebar-expand" aria-label="The sidebar icon" %} in the top right.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
1. Navigate to your project.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||

|
||||
2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.
|
||||

|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %} to open the menu.
|
||||
|
||||

|
||||
|
||||
2. In the menu, click {% octicon "gear" aria-hidden="true" %} **Settings** to access the project settings.
|
||||
|
||||
@@ -1,7 +1,8 @@
|
||||
1. To show closed projects, above the list of projects click **X Closed**.
|
||||
1. Click the project you want to reopen.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %} to open the menu.
|
||||

|
||||
|
||||

|
||||
|
||||
1. In the menu, click {% octicon "gear" aria-hidden="true" %} **Settings** to access the project settings.
|
||||

|
||||
1. In the "Danger Zone" section, click **Re-open this project**.
|
||||
|
||||
@@ -1,3 +1,2 @@
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click **Save changes**.
|
||||

|
||||
|
||||