Making the projects v1 screenshots accessible (#36662)
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
This commit is contained in:
Steve Guntrip
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.5 KiB After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.6 KiB After Width: | Height: | Size: 7.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 28 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.6 KiB After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 90 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.7 KiB After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 16 KiB |
@@ -26,10 +26,8 @@ A collaborator is a person who has permissions to a project board you own. A col
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
|
||||
|
||||
|
||||
## Removing a collaborator from a user-owned project board
|
||||
|
||||
|
||||
@@ -60,8 +60,6 @@ You can use templates to quickly set up a new {% data variables.projects.project
|
||||
|
||||
For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards)."
|
||||
|
||||
|
||||
|
||||
{% data reusables.project-management.copy-project-boards %}
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -19,10 +19,9 @@ When you close a {% data variables.projects.projects_v1_board %}, any configured
|
||||
If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)" or "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards)."
|
||||
|
||||
1. Navigate to the list of {% data variables.projects.projects_v1_boards %} in your repository or organization, or owned by your personal account.
|
||||
2. In the projects list, next to the {% data variables.projects.projects_v1_board %} you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
|
||||
|
||||
2. In the projects list, next to the {% data variables.projects.projects_v1_board %} you want to close, click {% octicon "kebab-horizontal" aria-label="Project menu" %}.
|
||||
|
||||
3. Click **Close**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -31,14 +31,11 @@ allowTitleToDifferFromFilename: true
|
||||
{% endtip %}
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate.
|
||||
2. In the column you want to automate, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
|
||||
2. In the column you want to automate, click {% octicon "kebab-horizontal" aria-label="Column menu" %}.
|
||||
|
||||
3. Click **Manage automation**.
|
||||
|
||||
4. Using the Preset drop-down menu, select an automation preset.
|
||||
|
||||
5. Select the workflow automations you want to configure for the column.
|
||||
|
||||
6. Click **Update automation**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -25,15 +25,10 @@ A {% data variables.projects.projects_v1_board %}'s automation is also enabled b
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**.
|
||||
|
||||
|
||||
4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board.
|
||||
|
||||
5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}.
|
||||
|
||||
6. Optionally, under "Description", type a description of the copied project board that other people will see.
|
||||
|
||||
7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards)."
|
||||
|
||||
{% data reusables.project-management.choose-visibility %}
|
||||
9. Click **Copy project**.
|
||||
|
||||
|
||||
@@ -35,9 +35,9 @@ You can also configure workflow automations to keep your {% data variables.proje
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
@@ -93,8 +93,7 @@ You can also configure workflow automations to keep your {% data variables.proje
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
|
||||
{% ifversion projects-v2 %}
|
||||
2. Under your repository name, click {% octicon "project" aria-hidden="true" %} **Projects**.{% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
|
||||
@@ -24,7 +24,6 @@ allowTitleToDifferFromFilename: true
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
|
||||
4. Click **Delete project**.
|
||||
|
||||
5. To confirm that you want to delete the project board, click **OK**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -25,7 +25,6 @@ allowTitleToDifferFromFilename: true
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
|
||||
4. Modify the {% data variables.projects.projects_v1_board %} name and description as needed, then click **Save project**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -22,13 +22,9 @@ Anyone with write permissions to a {% data variables.projects.projects_v1_board
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
4. In the left sidebar, click **Linked repositories**.
|
||||
|
||||
5. Click **Link a repository**.
|
||||
|
||||
6. Search for the repository you'd like to link.
|
||||
|
||||
7. Click **Link**. To unlink, click **Unlink**.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -22,9 +22,7 @@ When you reopen a {% data variables.projects.projects_v1_board %}, you have the
|
||||
{% data reusables.project-management.click-menu %}
|
||||
3. Choose whether to sync automation for your {% data variables.projects.projects_v1_board %} or reopen your {% data variables.projects.projects_v1_board %} without syncing.
|
||||
- To reopen your {% data variables.projects.projects_v1_board %} and sync automation, click **Reopen and sync project**.
|
||||
|
||||
- To reopen your {% data variables.projects.projects_v1_board %} without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -22,8 +22,6 @@ You can add issue or pull request cards to your {% data variables.projects.proje
|
||||
|
||||
You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board)."
|
||||
@@ -38,7 +36,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
|
||||
2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
|
||||
|
||||
|
||||
3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers such as `is:issue is:open`. For more information on search qualifiers you can use, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests)."
|
||||
|
||||
{% tip %}
|
||||
@@ -59,15 +57,14 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
||||
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
|
||||
|
||||
1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click the **Recent**, **Repository**, **User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to.
|
||||
|
||||
3. Type the name of the project in **Filter projects** field.
|
||||
|
||||
4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request.
|
||||
|
||||
5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
|
||||
|
||||
5. Click **Awaiting triage**{% octicon "triangle-down" aria-hidden="true" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -26,15 +26,12 @@ allowTitleToDifferFromFilename: true
|
||||
|
||||
When you add a URL for an issue, pull request, or another {% data variables.projects.projects_v1_board %} to a note, you'll see a preview in a summary card below your text.
|
||||
|
||||
|
||||
|
||||
## Adding notes to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add notes.
|
||||
2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}.
|
||||
|
||||
2. In the column you want to add a note to, click {% octicon "plus" aria-label="Add a note to this column" %}.
|
||||
|
||||
3. Type your note, then click **Add**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -57,11 +54,8 @@ When you convert a note to an issue, the issue is automatically created using th
|
||||
1. Navigate to the note that you want to convert to an issue.
|
||||
{% data reusables.project-management.project-note-more-options %}
|
||||
3. Click **Convert to issue**.
|
||||
|
||||
4. If the card is on an organization-wide {% data variables.projects.projects_v1_board %}, in the drop-down menu, choose the repository you want to add the issue to.
|
||||
|
||||
5. Optionally, edit the pre-filled issue title, and type an issue body.
|
||||
|
||||
6. Click **Convert to issue**.
|
||||
7. The note is automatically converted to an issue. In the {% data variables.projects.projects_v1_board %}, the new issue card will be in the same location as the previous note.
|
||||
|
||||
@@ -70,9 +64,7 @@ When you convert a note to an issue, the issue is automatically created using th
|
||||
1. Navigate to the note that you want to edit or remove.
|
||||
{% data reusables.project-management.project-note-more-options %}
|
||||
3. To edit the contents of the note, click **Edit note**.
|
||||
|
||||
4. To delete the contents of the notes, click **Delete note**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -18,15 +18,13 @@ Automation in your {% data variables.projects.projects_v1_board %} does not appl
|
||||
|
||||
## Archiving cards on a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. In a {% data variables.projects.projects_v1_board %}, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
|
||||
1. In a {% data variables.projects.projects_v1_board %}, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="Card menu" %}.
|
||||
|
||||
2. Click **Archive**.
|
||||
|
||||
|
||||
## Restoring cards on a {% data variables.projects.projects_v1_board %} from the sidebar
|
||||
|
||||
{% data reusables.project-management.click-menu %}
|
||||
2. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **View archive**.
|
||||
|
||||
2. Click {% octicon "kebab-horizontal" aria-label="Project menu" %}, then click **View archive**.
|
||||
|
||||
3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**.
|
||||
|
||||
|
||||
@@ -32,7 +32,6 @@ You can also use the "Filter cards" search bar at the top of each {% data variab
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} that contains the cards you want to filter.
|
||||
2. Above the project card columns, click into the "Filter cards" search bar and type a search query to filter the cards.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
||||
@@ -45,7 +45,7 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
||||
|
||||
|
||||
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)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -60,7 +60,5 @@ 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 %}
|
||||
|
||||
@@ -22,7 +22,7 @@ topics:
|
||||
|
||||
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.
|
||||
|
||||
@@ -26,11 +26,8 @@ shortTitle: Create a team discussion
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
6. Type a team discussion title and a comment to start a conversation.
|
||||
|
||||
7. Optionally, select whether you want your post to be private or public using the drop-down menu.
|
||||
|
||||
8. Click **Comment**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -25,9 +25,8 @@ shortTitle: Manage a team discussion
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
6. Click {% octicon "kebab-horizontal" aria-label="The edit icon" %} next to the team discussion you want to edit or delete.
|
||||
7. Click **Edit**. Optionally, click **Delete**.
|
||||
|
||||
|
||||
8. Modify the team discussion title and comment as needed, and click **Update comment**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -22,8 +22,7 @@ topics:
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
5. Click {% octicon "pin" aria-label="The pin icon" %} next to the team discussion you want to pin. You can also unpin a discussion by clicking the icon.
|
||||
|
||||
5. Click {% octicon "pin" aria-label="Pin this discussion" %} next to the team discussion you want to pin. You can also unpin a discussion by clicking the icon.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -29,6 +29,5 @@ An outside collaborator is a person who isn't explicitly a member of your organi
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
{% data reusables.project-management.collaborator-permissions %}
|
||||
|
||||
@@ -36,7 +36,6 @@ By default, organization members have write access to their organization's {% da
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
8. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**.
|
||||
|
||||
9. Click **Save**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -36,7 +36,6 @@ allowTitleToDifferFromFilename: true
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
9. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
{% data reusables.project-management.collaborator-permissions %}
|
||||
|
||||
|
||||
@@ -45,9 +45,7 @@ You can give an entire team the same permission level to a {% data variables.pro
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
1. In the left sidebar, click **Teams**.
|
||||
1. To add a team, click **Add a team: Select team**. Then, choose a team from the dropdown menu or search for the team you'd like to add.
|
||||
|
||||
1. Next to the team name, use the dropdown menu to select the desired permission level: **Read**, **Write**, or **Admin**.
|
||||
|
||||
|
||||
## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
|
||||
@@ -31,7 +31,6 @@ When you disable project boards, you will no longer see project board informatio
|
||||
1. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
|
||||
- To disable organization-wide project boards, unselect **Enable projects for the organization**.
|
||||
- To disable repository project boards in the organization, unselect **Enable projects for all repositories**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% data reusables.organizations.disable_project_board_results %}
|
||||
|
||||
@@ -21,6 +21,5 @@ When you disable {% data variables.projects.projects_v1_boards %}, you will no l
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under "Features," unselect the **Projects** checkbox.
|
||||
|
||||
|
||||
After {% data variables.projects.projects_v1_boards %} are disabled, existing {% data variables.projects.projects_v1_boards %} are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %}
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Settings**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. On your new project board, to add your first column, **Add a column**.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
5. Optionally, to add a template to your project board, use the **Template:** drop-down menu and click a template.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Under "Visibility", choose to make your project board {% ifversion ghae %}internal{% else %}public{% endif %} or private. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)."
|
||||
|
||||
![Radio buttons to choose project board visibility]{% ifversion ghae %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% elsif ghes > 3.4 %}(/assets/images/help/projects/visibility-radio-buttons-es.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %}
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
8. In the left sidebar, click **Collaborators**.
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
11. Optionally, next to the new collaborator's name, use the drop-down menu and click the desired permission level: **Read**, **Write**, or **Admin**.
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Type a name and description for your project board.
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Optionally, under **Linked repositories**, search for a repository you'd like to link to your project board.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Under "Column name", type the name of the column you want to create.
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. In the upper-right corner of the notes, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
|
||||
1. In the upper-right corner of the notes, click {% octicon "kebab-horizontal" aria-label="Card menu" %}.
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
4. Next to the collaborator you want to remove, click **X**.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Select the workflow automations you want to configure for the column.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. Optionally, under "Automation", select an automation preset using the drop-down menu.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1 @@
|
||||
1. In the projects list, click the name of the {% data variables.projects.projects_v1_board %}.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user