diff --git a/assets/images/help/issues/migrate-menu-item.png b/assets/images/help/issues/migrate-menu-item.png new file mode 100644 index 0000000000..db189ea475 Binary files /dev/null and b/assets/images/help/issues/migrate-menu-item.png differ diff --git a/assets/images/help/issues/migrate-option.png b/assets/images/help/issues/migrate-option.png index 000c38f814..b82f0de40c 100644 Binary files a/assets/images/help/issues/migrate-option.png and b/assets/images/help/issues/migrate-option.png differ diff --git a/assets/images/help/issues/migrate-to-beta.png b/assets/images/help/issues/migrate-to-beta.png deleted file mode 100644 index d2509a67e8..0000000000 Binary files a/assets/images/help/issues/migrate-to-beta.png and /dev/null differ diff --git a/assets/images/help/issues/project_side_bar.png b/assets/images/help/issues/project_side_bar.png deleted file mode 100644 index 60f9ad26fb..0000000000 Binary files a/assets/images/help/issues/project_side_bar.png and /dev/null differ diff --git a/assets/images/help/issues/projects-beta-assign-button.png b/assets/images/help/issues/projects-beta-assign-button.png deleted file mode 100644 index fb2d23e8ca..0000000000 Binary files a/assets/images/help/issues/projects-beta-assign-button.png and /dev/null differ diff --git a/assets/images/help/issues/projects-beta-assign-dropdown.png b/assets/images/help/issues/projects-beta-assign-dropdown.png deleted file mode 100644 index 66fffb8f6d..0000000000 Binary files a/assets/images/help/issues/projects-beta-assign-dropdown.png and /dev/null differ diff --git a/assets/images/help/issues/projects-classic-org.png b/assets/images/help/issues/projects-classic-org.png index 8a9b474691..461b5d77c0 100644 Binary files a/assets/images/help/issues/projects-classic-org.png and b/assets/images/help/issues/projects-classic-org.png differ diff --git a/assets/images/help/issues/projects-classic-user.png b/assets/images/help/issues/projects-classic-user.png index 0f628bb786..47131211cd 100644 Binary files a/assets/images/help/issues/projects-classic-user.png and b/assets/images/help/issues/projects-classic-user.png differ diff --git a/assets/images/help/projects-v2/access-change-role.png b/assets/images/help/projects-v2/access-change-role.png new file mode 100644 index 0000000000..1e9035927d Binary files /dev/null and b/assets/images/help/projects-v2/access-change-role.png differ diff --git a/assets/images/help/projects-v2/access-find-member.png b/assets/images/help/projects-v2/access-find-member.png new file mode 100644 index 0000000000..42e8dd643e Binary files /dev/null and b/assets/images/help/projects-v2/access-find-member.png differ diff --git a/assets/images/help/projects-v2/access-invite.png b/assets/images/help/projects-v2/access-invite.png new file mode 100644 index 0000000000..e944c7d1ae Binary files /dev/null and b/assets/images/help/projects-v2/access-invite.png differ diff --git a/assets/images/help/projects-v2/access-remove-member.png b/assets/images/help/projects-v2/access-remove-member.png new file mode 100644 index 0000000000..4cbc0cde9e Binary files /dev/null and b/assets/images/help/projects-v2/access-remove-member.png differ diff --git a/assets/images/help/projects-v2/access-role.png b/assets/images/help/projects-v2/access-role.png new file mode 100644 index 0000000000..5ed6e7ea56 Binary files /dev/null and b/assets/images/help/projects-v2/access-role.png differ diff --git a/assets/images/help/projects-v2/access-search.png b/assets/images/help/projects-v2/access-search.png new file mode 100644 index 0000000000..e4ba4a5542 Binary files /dev/null and b/assets/images/help/projects-v2/access-search.png differ diff --git a/assets/images/help/projects-v2/add-bulk-menu-item.png b/assets/images/help/projects-v2/add-bulk-menu-item.png new file mode 100644 index 0000000000..f7587853de Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-menu-item.png differ diff --git a/assets/images/help/projects-v2/add-bulk-save.png b/assets/images/help/projects-v2/add-bulk-save.png new file mode 100644 index 0000000000..c9c9e01ee3 Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-save.png differ diff --git a/assets/images/help/projects-v2/add-bulk-select-issues.png b/assets/images/help/projects-v2/add-bulk-select-issues.png new file mode 100644 index 0000000000..17326af6f9 Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-select-issues.png differ diff --git a/assets/images/help/projects-v2/add-bulk-select-repo.png b/assets/images/help/projects-v2/add-bulk-select-repo.png new file mode 100644 index 0000000000..17fe064c6c Binary files /dev/null and b/assets/images/help/projects-v2/add-bulk-select-repo.png differ diff --git a/assets/images/help/projects-v2/add-draft-issue.png b/assets/images/help/projects-v2/add-draft-issue.png new file mode 100644 index 0000000000..3a85f9ba17 Binary files /dev/null and b/assets/images/help/projects-v2/add-draft-issue.png differ diff --git a/assets/images/help/projects-v2/add-item-select-issue.png b/assets/images/help/projects-v2/add-item-select-issue.png new file mode 100644 index 0000000000..80bb4eb283 Binary files /dev/null and b/assets/images/help/projects-v2/add-item-select-issue.png differ diff --git a/assets/images/help/projects-v2/add-item-select-repo.png b/assets/images/help/projects-v2/add-item-select-repo.png new file mode 100644 index 0000000000..f980aa879d Binary files /dev/null and b/assets/images/help/projects-v2/add-item-select-repo.png differ diff --git a/assets/images/help/projects-v2/add-item.png b/assets/images/help/projects-v2/add-item.png new file mode 100644 index 0000000000..304b27362b Binary files /dev/null and b/assets/images/help/projects-v2/add-item.png differ diff --git a/assets/images/help/projects-v2/add-iteration-options.png b/assets/images/help/projects-v2/add-iteration-options.png new file mode 100644 index 0000000000..277e4e5a60 Binary files /dev/null and b/assets/images/help/projects-v2/add-iteration-options.png differ diff --git a/assets/images/help/projects-v2/add-iteration.png b/assets/images/help/projects-v2/add-iteration.png new file mode 100644 index 0000000000..68e0239387 Binary files /dev/null and b/assets/images/help/projects-v2/add-iteration.png differ diff --git a/assets/images/help/projects-v2/add-to-repo-button.png b/assets/images/help/projects-v2/add-to-repo-button.png new file mode 100644 index 0000000000..acbfe0b4e0 Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo-button.png differ diff --git a/assets/images/help/projects-v2/add-to-repo-search.png b/assets/images/help/projects-v2/add-to-repo-search.png new file mode 100644 index 0000000000..3f085c06f7 Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo-search.png differ diff --git a/assets/images/help/projects-v2/add-to-repo.png b/assets/images/help/projects-v2/add-to-repo.png new file mode 100644 index 0000000000..11bdb13d77 Binary files /dev/null and b/assets/images/help/projects-v2/add-to-repo.png differ diff --git a/assets/images/help/projects-v2/archive-item-prompt.png b/assets/images/help/projects-v2/archive-item-prompt.png new file mode 100644 index 0000000000..96e538f0ab Binary files /dev/null and b/assets/images/help/projects-v2/archive-item-prompt.png differ diff --git a/assets/images/help/projects-v2/archive-menu-item.png b/assets/images/help/projects-v2/archive-menu-item.png new file mode 100644 index 0000000000..1334383c81 Binary files /dev/null and b/assets/images/help/projects-v2/archive-menu-item.png differ diff --git a/assets/images/help/projects-v2/archived-items-menu-item.png b/assets/images/help/projects-v2/archived-items-menu-item.png new file mode 100644 index 0000000000..126366ad91 Binary files /dev/null and b/assets/images/help/projects-v2/archived-items-menu-item.png differ diff --git a/assets/images/help/projects-v2/base-role.png b/assets/images/help/projects-v2/base-role.png new file mode 100644 index 0000000000..040cfaae67 Binary files /dev/null and b/assets/images/help/projects-v2/base-role.png differ diff --git a/assets/images/help/projects-v2/column-field-menu-item.png b/assets/images/help/projects-v2/column-field-menu-item.png new file mode 100644 index 0000000000..c595dbda99 Binary files /dev/null and b/assets/images/help/projects-v2/column-field-menu-item.png differ diff --git a/assets/images/help/projects-v2/column-field-menu.png b/assets/images/help/projects-v2/column-field-menu.png new file mode 100644 index 0000000000..42ef78b338 Binary files /dev/null and b/assets/images/help/projects-v2/column-field-menu.png differ diff --git a/assets/images/help/projects-v2/convert-to-issue-select-repo.png b/assets/images/help/projects-v2/convert-to-issue-select-repo.png new file mode 100644 index 0000000000..b60dba20ba Binary files /dev/null and b/assets/images/help/projects-v2/convert-to-issue-select-repo.png differ diff --git a/assets/images/help/projects-v2/default-workflows.png b/assets/images/help/projects-v2/default-workflows.png new file mode 100644 index 0000000000..7bd1ad21ab Binary files /dev/null and b/assets/images/help/projects-v2/default-workflows.png differ diff --git a/assets/images/help/projects-v2/delete-field.png b/assets/images/help/projects-v2/delete-field.png new file mode 100644 index 0000000000..06b7d2caba Binary files /dev/null and b/assets/images/help/projects-v2/delete-field.png differ diff --git a/assets/images/help/projects-v2/delete-item-prompt.png b/assets/images/help/projects-v2/delete-item-prompt.png new file mode 100644 index 0000000000..d08b136361 Binary files /dev/null and b/assets/images/help/projects-v2/delete-item-prompt.png differ diff --git a/assets/images/help/projects-v2/delete-menu-item.png b/assets/images/help/projects-v2/delete-menu-item.png new file mode 100644 index 0000000000..dc8fa19e29 Binary files /dev/null and b/assets/images/help/projects-v2/delete-menu-item.png differ diff --git a/assets/images/help/projects-v2/delete-view.png b/assets/images/help/projects-v2/delete-view.png new file mode 100644 index 0000000000..972c1aa865 Binary files /dev/null and b/assets/images/help/projects-v2/delete-view.png differ diff --git a/assets/images/help/projects-v2/disable-insights-checkbox.png b/assets/images/help/projects-v2/disable-insights-checkbox.png new file mode 100644 index 0000000000..8edadc91cb Binary files /dev/null and b/assets/images/help/projects-v2/disable-insights-checkbox.png differ diff --git a/assets/images/help/projects-v2/disable-insights-save.png b/assets/images/help/projects-v2/disable-insights-save.png new file mode 100644 index 0000000000..af9f98cc26 Binary files /dev/null and b/assets/images/help/projects-v2/disable-insights-save.png differ diff --git a/assets/images/help/projects-v2/duplicate-view.png b/assets/images/help/projects-v2/duplicate-view.png new file mode 100644 index 0000000000..df93335cf3 Binary files /dev/null and b/assets/images/help/projects-v2/duplicate-view.png differ diff --git a/assets/images/help/projects-v2/edit-description.png b/assets/images/help/projects-v2/edit-description.png new file mode 100644 index 0000000000..ac5ce06f97 Binary files /dev/null and b/assets/images/help/projects-v2/edit-description.png differ diff --git a/assets/images/help/projects-v2/edit-readme.png b/assets/images/help/projects-v2/edit-readme.png new file mode 100644 index 0000000000..bd56e455d8 Binary files /dev/null and b/assets/images/help/projects-v2/edit-readme.png differ diff --git a/assets/images/help/projects-v2/features-org-menu.png b/assets/images/help/projects-v2/features-org-menu.png new file mode 100644 index 0000000000..98b51746c3 Binary files /dev/null and b/assets/images/help/projects-v2/features-org-menu.png differ diff --git a/assets/images/help/projects-v2/field-options.png b/assets/images/help/projects-v2/field-options.png new file mode 100644 index 0000000000..c463fab9ce Binary files /dev/null and b/assets/images/help/projects-v2/field-options.png differ diff --git a/assets/images/help/projects-v2/field-rename.png b/assets/images/help/projects-v2/field-rename.png new file mode 100644 index 0000000000..efbd9a5ce4 Binary files /dev/null and b/assets/images/help/projects-v2/field-rename.png differ diff --git a/assets/images/help/projects-v2/group-menu-item.png b/assets/images/help/projects-v2/group-menu-item.png new file mode 100644 index 0000000000..69d947b78c Binary files /dev/null and b/assets/images/help/projects-v2/group-menu-item.png differ diff --git a/assets/images/help/projects-v2/group-menu.png b/assets/images/help/projects-v2/group-menu.png new file mode 100644 index 0000000000..16d42272cd Binary files /dev/null and b/assets/images/help/projects-v2/group-menu.png differ diff --git a/assets/images/help/projects-v2/hide-field-via-menu.png b/assets/images/help/projects-v2/hide-field-via-menu.png new file mode 100644 index 0000000000..ee32c7be6d Binary files /dev/null and b/assets/images/help/projects-v2/hide-field-via-menu.png differ diff --git a/assets/images/help/projects-v2/insights-button.png b/assets/images/help/projects-v2/insights-button.png new file mode 100644 index 0000000000..505114ac67 Binary files /dev/null and b/assets/images/help/projects-v2/insights-button.png differ diff --git a/assets/images/help/projects-v2/insights-configure.png b/assets/images/help/projects-v2/insights-configure.png new file mode 100644 index 0000000000..d63893cfd1 Binary files /dev/null and b/assets/images/help/projects-v2/insights-configure.png differ diff --git a/assets/images/help/projects-v2/insights-group.png b/assets/images/help/projects-v2/insights-group.png new file mode 100644 index 0000000000..5fbee6c061 Binary files /dev/null and b/assets/images/help/projects-v2/insights-group.png differ diff --git a/assets/images/help/projects-v2/insights-layout.png b/assets/images/help/projects-v2/insights-layout.png new file mode 100644 index 0000000000..4d1803d920 Binary files /dev/null and b/assets/images/help/projects-v2/insights-layout.png differ diff --git a/assets/images/help/projects-v2/insights-new-chart.png b/assets/images/help/projects-v2/insights-new-chart.png new file mode 100644 index 0000000000..002cf007c5 Binary files /dev/null and b/assets/images/help/projects-v2/insights-new-chart.png differ diff --git a/assets/images/help/projects-v2/insights-rename.png b/assets/images/help/projects-v2/insights-rename.png new file mode 100644 index 0000000000..06d650d586 Binary files /dev/null and b/assets/images/help/projects-v2/insights-rename.png differ diff --git a/assets/images/help/projects-v2/insights-save-filter.png b/assets/images/help/projects-v2/insights-save-filter.png new file mode 100644 index 0000000000..483b2cd843 Binary files /dev/null and b/assets/images/help/projects-v2/insights-save-filter.png differ diff --git a/assets/images/help/projects-v2/insights-save.png b/assets/images/help/projects-v2/insights-save.png new file mode 100644 index 0000000000..634b60dca2 Binary files /dev/null and b/assets/images/help/projects-v2/insights-save.png differ diff --git a/assets/images/help/projects-v2/insights-select-a-chart.png b/assets/images/help/projects-v2/insights-select-a-chart.png new file mode 100644 index 0000000000..b0a61995ea Binary files /dev/null and b/assets/images/help/projects-v2/insights-select-a-chart.png differ diff --git a/assets/images/help/projects-v2/insights-x-axis.png b/assets/images/help/projects-v2/insights-x-axis.png new file mode 100644 index 0000000000..68133f22e3 Binary files /dev/null and b/assets/images/help/projects-v2/insights-x-axis.png differ diff --git a/assets/images/help/projects-v2/insights-y-axis.png b/assets/images/help/projects-v2/insights-y-axis.png new file mode 100644 index 0000000000..07fa9f9147 Binary files /dev/null and b/assets/images/help/projects-v2/insights-y-axis.png differ diff --git a/assets/images/help/projects-v2/issue-edit-project-sidebar.png b/assets/images/help/projects-v2/issue-edit-project-sidebar.png new file mode 100644 index 0000000000..4c2033c00d Binary files /dev/null and b/assets/images/help/projects-v2/issue-edit-project-sidebar.png differ diff --git a/assets/images/help/projects-v2/issue-index-project-menu.png b/assets/images/help/projects-v2/issue-index-project-menu.png new file mode 100644 index 0000000000..5f9a806171 Binary files /dev/null and b/assets/images/help/projects-v2/issue-index-project-menu.png differ diff --git a/assets/images/help/projects-v2/issue-index-select-project.png b/assets/images/help/projects-v2/issue-index-select-project.png new file mode 100644 index 0000000000..2c4dc91845 Binary files /dev/null and b/assets/images/help/projects-v2/issue-index-select-project.png differ diff --git a/assets/images/help/projects-v2/issue-sidebar-projects.png b/assets/images/help/projects-v2/issue-sidebar-projects.png new file mode 100644 index 0000000000..8b898a9009 Binary files /dev/null and b/assets/images/help/projects-v2/issue-sidebar-projects.png differ diff --git a/assets/images/help/projects-v2/issue-sidebar-select-project.png b/assets/images/help/projects-v2/issue-sidebar-select-project.png new file mode 100644 index 0000000000..7ecb60f6cb Binary files /dev/null and b/assets/images/help/projects-v2/issue-sidebar-select-project.png differ diff --git a/assets/images/help/projects-v2/item-context-menu-button-board.png b/assets/images/help/projects-v2/item-context-menu-button-board.png new file mode 100644 index 0000000000..8aa8953f85 Binary files /dev/null and b/assets/images/help/projects-v2/item-context-menu-button-board.png differ diff --git a/assets/images/help/projects-v2/item-context-menu-button-table.png b/assets/images/help/projects-v2/item-context-menu-button-table.png new file mode 100644 index 0000000000..c58e57b9f2 Binary files /dev/null and b/assets/images/help/projects-v2/item-context-menu-button-table.png differ diff --git a/assets/images/help/projects-v2/item-convert-to-issue.png b/assets/images/help/projects-v2/item-convert-to-issue.png new file mode 100644 index 0000000000..2e370d65a2 Binary files /dev/null and b/assets/images/help/projects-v2/item-convert-to-issue.png differ diff --git a/assets/images/help/projects-v2/iteration-date.png b/assets/images/help/projects-v2/iteration-date.png new file mode 100644 index 0000000000..785bed72c9 Binary files /dev/null and b/assets/images/help/projects-v2/iteration-date.png differ diff --git a/assets/images/help/projects-v2/iteration-delete.png b/assets/images/help/projects-v2/iteration-delete.png new file mode 100644 index 0000000000..4532c93ff9 Binary files /dev/null and b/assets/images/help/projects-v2/iteration-delete.png differ diff --git a/assets/images/help/projects-v2/iteration-field-duration.png b/assets/images/help/projects-v2/iteration-field-duration.png new file mode 100644 index 0000000000..18f1bb4ed0 Binary files /dev/null and b/assets/images/help/projects-v2/iteration-field-duration.png differ diff --git a/assets/images/help/projects-v2/iteration-field-starts.png b/assets/images/help/projects-v2/iteration-field-starts.png new file mode 100644 index 0000000000..8d3c017718 Binary files /dev/null and b/assets/images/help/projects-v2/iteration-field-starts.png differ diff --git a/assets/images/help/projects-v2/iteration-rename.png b/assets/images/help/projects-v2/iteration-rename.png new file mode 100644 index 0000000000..a7a7e97fbf Binary files /dev/null and b/assets/images/help/projects-v2/iteration-rename.png differ diff --git a/assets/images/help/projects-v2/iteration-save.png b/assets/images/help/projects-v2/iteration-save.png new file mode 100644 index 0000000000..d866cdde82 Binary files /dev/null and b/assets/images/help/projects-v2/iteration-save.png differ diff --git a/assets/images/help/projects-v2/manage-access.png b/assets/images/help/projects-v2/manage-access.png new file mode 100644 index 0000000000..cd936781dc Binary files /dev/null and b/assets/images/help/projects-v2/manage-access.png differ diff --git a/assets/images/help/projects-v2/modify-field-menu.png b/assets/images/help/projects-v2/modify-field-menu.png new file mode 100644 index 0000000000..9edf9c0084 Binary files /dev/null and b/assets/images/help/projects-v2/modify-field-menu.png differ diff --git a/assets/images/help/projects-v2/new-field-button.png b/assets/images/help/projects-v2/new-field-button.png new file mode 100644 index 0000000000..eb6dbfb5e1 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-button.png differ diff --git a/assets/images/help/projects-v2/new-field-date.png b/assets/images/help/projects-v2/new-field-date.png new file mode 100644 index 0000000000..528b1e45d6 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-date.png differ diff --git a/assets/images/help/projects-v2/new-field-iteration.png b/assets/images/help/projects-v2/new-field-iteration.png new file mode 100644 index 0000000000..f020571335 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-iteration.png differ diff --git a/assets/images/help/projects-v2/new-field-menu-item.png b/assets/images/help/projects-v2/new-field-menu-item.png new file mode 100644 index 0000000000..5cddaf95cc Binary files /dev/null and b/assets/images/help/projects-v2/new-field-menu-item.png differ diff --git a/assets/images/help/projects-v2/new-field-name.png b/assets/images/help/projects-v2/new-field-name.png new file mode 100644 index 0000000000..4a6e4d4dea Binary files /dev/null and b/assets/images/help/projects-v2/new-field-name.png differ diff --git a/assets/images/help/projects-v2/new-field-number.png b/assets/images/help/projects-v2/new-field-number.png new file mode 100644 index 0000000000..9ecb3018cb Binary files /dev/null and b/assets/images/help/projects-v2/new-field-number.png differ diff --git a/assets/images/help/projects-v2/new-field-save-and-create.png b/assets/images/help/projects-v2/new-field-save-and-create.png new file mode 100644 index 0000000000..0e19469aef Binary files /dev/null and b/assets/images/help/projects-v2/new-field-save-and-create.png differ diff --git a/assets/images/help/projects-v2/new-field-save.png b/assets/images/help/projects-v2/new-field-save.png new file mode 100644 index 0000000000..09fe39b537 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-save.png differ diff --git a/assets/images/help/projects-v2/new-field-single-select.png b/assets/images/help/projects-v2/new-field-single-select.png new file mode 100644 index 0000000000..11d6f14df3 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-single-select.png differ diff --git a/assets/images/help/projects-v2/new-field-text.png b/assets/images/help/projects-v2/new-field-text.png new file mode 100644 index 0000000000..85ae6512b1 Binary files /dev/null and b/assets/images/help/projects-v2/new-field-text.png differ diff --git a/assets/images/help/projects-v2/new-project-button.png b/assets/images/help/projects-v2/new-project-button.png new file mode 100644 index 0000000000..ebfd1f38a2 Binary files /dev/null and b/assets/images/help/projects-v2/new-project-button.png differ diff --git a/assets/images/help/projects-v2/new-view.png b/assets/images/help/projects-v2/new-view.png new file mode 100644 index 0000000000..fd6a93fc13 Binary files /dev/null and b/assets/images/help/projects-v2/new-view.png differ diff --git a/assets/images/help/projects-v2/no-grouping.png b/assets/images/help/projects-v2/no-grouping.png new file mode 100644 index 0000000000..81399b8b4a Binary files /dev/null and b/assets/images/help/projects-v2/no-grouping.png differ diff --git a/assets/images/help/projects-v2/no-sorting.png b/assets/images/help/projects-v2/no-sorting.png new file mode 100644 index 0000000000..a572350873 Binary files /dev/null and b/assets/images/help/projects-v2/no-sorting.png differ diff --git a/assets/images/help/projects-v2/omnibar-add.png b/assets/images/help/projects-v2/omnibar-add.png new file mode 100644 index 0000000000..6712eb271c Binary files /dev/null and b/assets/images/help/projects-v2/omnibar-add.png differ diff --git a/assets/images/help/projects-v2/open-menu.png b/assets/images/help/projects-v2/open-menu.png new file mode 100644 index 0000000000..c4f2499f8e Binary files /dev/null and b/assets/images/help/projects-v2/open-menu.png differ diff --git a/assets/images/help/projects-v2/paste-url-to-add.png b/assets/images/help/projects-v2/paste-url-to-add.png new file mode 100644 index 0000000000..ae3e122bc7 Binary files /dev/null and b/assets/images/help/projects-v2/paste-url-to-add.png differ diff --git a/assets/images/help/projects-v2/priority-example.png b/assets/images/help/projects-v2/priority-example.png new file mode 100644 index 0000000000..af600b55ed Binary files /dev/null and b/assets/images/help/projects-v2/priority-example.png differ diff --git a/assets/images/help/projects-v2/rename-view.png b/assets/images/help/projects-v2/rename-view.png new file mode 100644 index 0000000000..eac8fa3840 Binary files /dev/null and b/assets/images/help/projects-v2/rename-view.png differ diff --git a/assets/images/help/projects-v2/repo-tab.png b/assets/images/help/projects-v2/repo-tab.png new file mode 100644 index 0000000000..9ac50b15cb Binary files /dev/null and b/assets/images/help/projects-v2/repo-tab.png differ diff --git a/assets/images/help/projects-v2/save-options.png b/assets/images/help/projects-v2/save-options.png new file mode 100644 index 0000000000..119b6e1675 Binary files /dev/null and b/assets/images/help/projects-v2/save-options.png differ diff --git a/assets/images/help/projects-v2/save-readme-button.png b/assets/images/help/projects-v2/save-readme-button.png new file mode 100644 index 0000000000..4fb7911a50 Binary files /dev/null and b/assets/images/help/projects-v2/save-readme-button.png differ diff --git a/assets/images/help/projects-v2/save-view.png b/assets/images/help/projects-v2/save-view.png new file mode 100644 index 0000000000..eb1a31a302 Binary files /dev/null and b/assets/images/help/projects-v2/save-view.png differ diff --git a/assets/images/help/projects-v2/select-field-header.png b/assets/images/help/projects-v2/select-field-header.png new file mode 100644 index 0000000000..aced6ab291 Binary files /dev/null and b/assets/images/help/projects-v2/select-field-header.png differ diff --git a/assets/images/help/projects-v2/select-iteration-field.png b/assets/images/help/projects-v2/select-iteration-field.png new file mode 100644 index 0000000000..b7882249ca Binary files /dev/null and b/assets/images/help/projects-v2/select-iteration-field.png differ diff --git a/assets/images/help/projects-v2/select-row-number.png b/assets/images/help/projects-v2/select-row-number.png new file mode 100644 index 0000000000..58bd09e5c2 Binary files /dev/null and b/assets/images/help/projects-v2/select-row-number.png differ diff --git a/assets/images/help/projects-v2/select-single-select.png b/assets/images/help/projects-v2/select-single-select.png new file mode 100644 index 0000000000..93fef4afa3 Binary files /dev/null and b/assets/images/help/projects-v2/select-single-select.png differ diff --git a/assets/images/help/projects-v2/settings-menu-item.png b/assets/images/help/projects-v2/settings-menu-item.png new file mode 100644 index 0000000000..ff8e781f87 Binary files /dev/null and b/assets/images/help/projects-v2/settings-menu-item.png differ diff --git a/assets/images/help/projects-v2/show-hide-fields-menu-item.png b/assets/images/help/projects-v2/show-hide-fields-menu-item.png new file mode 100644 index 0000000000..386e52f398 Binary files /dev/null and b/assets/images/help/projects-v2/show-hide-fields-menu-item.png differ diff --git a/assets/images/help/projects-v2/show-hide-fields.png b/assets/images/help/projects-v2/show-hide-fields.png new file mode 100644 index 0000000000..671af32ea7 Binary files /dev/null and b/assets/images/help/projects-v2/show-hide-fields.png differ diff --git a/assets/images/help/projects-v2/single-select-create-with-options.png b/assets/images/help/projects-v2/single-select-create-with-options.png new file mode 100644 index 0000000000..259bc4ca7d Binary files /dev/null and b/assets/images/help/projects-v2/single-select-create-with-options.png differ diff --git a/assets/images/help/projects-v2/single-select-delete.png b/assets/images/help/projects-v2/single-select-delete.png new file mode 100644 index 0000000000..c09b2edfd3 Binary files /dev/null and b/assets/images/help/projects-v2/single-select-delete.png differ diff --git a/assets/images/help/projects-v2/single-select-edit-options.png b/assets/images/help/projects-v2/single-select-edit-options.png new file mode 100644 index 0000000000..252361a4cb Binary files /dev/null and b/assets/images/help/projects-v2/single-select-edit-options.png differ diff --git a/assets/images/help/projects-v2/sort-menu-item.png b/assets/images/help/projects-v2/sort-menu-item.png new file mode 100644 index 0000000000..bf700aa784 Binary files /dev/null and b/assets/images/help/projects-v2/sort-menu-item.png differ diff --git a/assets/images/help/projects-v2/sort-menu.png b/assets/images/help/projects-v2/sort-menu.png new file mode 100644 index 0000000000..154f3c13a7 Binary files /dev/null and b/assets/images/help/projects-v2/sort-menu.png differ diff --git a/assets/images/help/projects-v2/sort-order.png b/assets/images/help/projects-v2/sort-order.png new file mode 100644 index 0000000000..04dcc5952d Binary files /dev/null and b/assets/images/help/projects-v2/sort-order.png differ diff --git a/assets/images/help/projects-v2/tab-projects.png b/assets/images/help/projects-v2/tab-projects.png new file mode 100644 index 0000000000..aa7e13969c Binary files /dev/null and b/assets/images/help/projects-v2/tab-projects.png differ diff --git a/assets/images/help/projects-v2/table-or-board.png b/assets/images/help/projects-v2/table-or-board.png new file mode 100644 index 0000000000..a653cc9aa7 Binary files /dev/null and b/assets/images/help/projects-v2/table-or-board.png differ diff --git a/assets/images/help/projects-v2/view-menu-icon.png b/assets/images/help/projects-v2/view-menu-icon.png new file mode 100644 index 0000000000..a2748c5efe Binary files /dev/null and b/assets/images/help/projects-v2/view-menu-icon.png differ diff --git a/assets/images/help/projects-v2/visibility-change-checkbox.png b/assets/images/help/projects-v2/visibility-change-checkbox.png new file mode 100644 index 0000000000..04f72da917 Binary files /dev/null and b/assets/images/help/projects-v2/visibility-change-checkbox.png differ diff --git a/assets/images/help/projects-v2/visibility.png b/assets/images/help/projects-v2/visibility.png new file mode 100644 index 0000000000..8083f1b36a Binary files /dev/null and b/assets/images/help/projects-v2/visibility.png differ diff --git a/assets/images/help/projects-v2/workflow-enable.png b/assets/images/help/projects-v2/workflow-enable.png new file mode 100644 index 0000000000..0c15d2b214 Binary files /dev/null and b/assets/images/help/projects-v2/workflow-enable.png differ diff --git a/assets/images/help/projects-v2/workflow-set.png b/assets/images/help/projects-v2/workflow-set.png new file mode 100644 index 0000000000..a2dab2f374 Binary files /dev/null and b/assets/images/help/projects-v2/workflow-set.png differ diff --git a/assets/images/help/projects-v2/workflow-when.png b/assets/images/help/projects-v2/workflow-when.png new file mode 100644 index 0000000000..486d6967fa Binary files /dev/null and b/assets/images/help/projects-v2/workflow-when.png differ diff --git a/assets/images/help/projects-v2/workflows-menu-item.png b/assets/images/help/projects-v2/workflows-menu-item.png new file mode 100644 index 0000000000..df39c56268 Binary files /dev/null and b/assets/images/help/projects-v2/workflows-menu-item.png differ diff --git a/content/actions/using-workflows/events-that-trigger-workflows.md b/content/actions/using-workflows/events-that-trigger-workflows.md index 9a4754b54a..375b5a3e4d 100644 --- a/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/content/actions/using-workflows/events-that-trigger-workflows.md @@ -447,7 +447,7 @@ on: {% ifversion fpt or ghec %} {% note %} -**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. {% endnote %} {% endif %} @@ -485,7 +485,7 @@ on: {% ifversion fpt or ghec %} {% note %} -**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. {% endnote %} {% endif %} @@ -523,7 +523,7 @@ on: {% ifversion fpt or ghec %} {% note %} -**Note**: This event does not occur for projects (beta). For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. {% endnote %} {% endif %} diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 53f6ef7258..4c739faea6 100644 --- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -889,20 +889,20 @@ Action | Description | `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)." | `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." -{%- ifversion fpt or ghec %} +{%- ifversion projects-v2 %} ## `project_field` category actions | Action | Description |--------|------------- -| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." -| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." +| `project_field.create` | A field was created in a project board. For more information, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." +| `project_field.delete` | A field was deleted in a project board. For more information, see "[Deleting fields](/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields)." ## `project_view` category actions | Action | Description |--------|------------- -| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)." -| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)." +| `project_view.create` | A view was created in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)." +| `project_view.delete` | A view was deleted in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)." {%- endif %} ## `protected_branch` category actions diff --git a/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index bd6c411282..6c4d45b193 100644 --- a/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -68,7 +68,7 @@ When you want to use an {% data variables.product.prodname_oauth_app %} that int | Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. | | Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. | | Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %} -| Projects | Access to user and organization projects (beta). Apps can request either read/write or read only access. |{% endif %} +| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %} ## Requesting updated permissions diff --git a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md index 19fe8cec31..ab83e4a820 100644 --- a/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md +++ b/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md @@ -34,8 +34,8 @@ When you block a user: - You are removed as a collaborator on their repositories - Their sponsorship of you is cancelled - Any pending repository or account successor invitations to or from the blocked user are cancelled -- The user is removed as a collaborator from all the Project Boards & Projects (beta) owned by you -- You are removed as a collaborator from all the Project Boards & Projects (beta) owned by the user +- The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you +- You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user After you've blocked a user, they cannot: - Send you any notifications, including by [@mentioning](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) your username @@ -48,8 +48,8 @@ After you've blocked a user, they cannot: - Cross-reference your repositories in comments - Fork, watch, pin, or star your repositories - Sponsor you -- Add you as a collaborator on their Project Boards & Projects (beta) -- Make changes to your public Project Boards & Projects (beta) +- Add you as a collaborator on their projects and {% data variables.projects.projects_v1_boards %} +- Make changes to your public projects and {% data variables.projects.projects_v1_boards %} In repositories you own, blocked users also cannot: - Open issues diff --git a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 32e1cda6ea..f834fa013e 100644 --- a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -64,8 +64,8 @@ Name | Description  `read:user`| Grants access to read a user's profile data.  `user:email`| Grants read access to a user's email addresses.  `user:follow`| Grants access to follow or unfollow other users.{% ifversion projects-oauth-scope %} -**`project`** | Grants read/write access to user and organization projects (beta). - `read:project`| Grants read only access to user and organization projects (beta).{% endif %} +**`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}. + `read:project`| Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %} **`delete_repo`** | Grants access to delete adminable repositories. **`write:discussion`** | Allows read and write access for team discussions.  `read:discussion` | Allows read access for team discussions. diff --git a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 7a2cbd07e4..c61a682e33 100644 --- a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -891,10 +891,10 @@ Key | Type | Description - Organization webhooks - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission -{% ifversion fpt or ghec %} +{% ifversion projects-v2 %} {% note %} -**Note**: This event does not occur for Projects (beta). +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. {% endnote %} {% endif %} @@ -923,10 +923,10 @@ Key | Type | Description - Organization webhooks - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission -{% ifversion fpt or ghec %} +{% ifversion projects-v2 %} {% note %} -**Note**: This event does not occur for Projects (beta). +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. {% endnote %} {% endif %} @@ -953,6 +953,14 @@ Key | Type | Description - Organization webhooks - {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +{% ifversion projects-v2 %} +{% note %} + +**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}. + +{% endnote %} +{% endif %} + ### Webhook payload object {% data reusables.webhooks.project_column_properties %} @@ -971,11 +979,11 @@ Key | Type | Description {% note %} -**Note:** Webhook events for Projects (beta) are currently in beta and subject to change. To share feedback about Projects (beta) webhooks with {% data variables.product.product_name %}, see the [Projects (beta) webhook feedback discussion](https://github.com/github/feedback/discussions/17405). +**Note:** Webhook events for {% data variables.projects.projects_v2 %} are currently in beta and subject to change. To share feedback about {% data variables.projects.projects_v2 %} webhooks with {% data variables.product.product_name %}, see the [Projects webhook feedback discussion](https://github.com/github/feedback/discussions/17405). {% endnote %} -Activity related to items in a Projects (beta) project. {% data reusables.webhooks.action_type_desc %} For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." +Activity related to items in a {% data variables.projects.project_v2 %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[About {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." ### Availability @@ -987,7 +995,7 @@ Activity related to items in a Projects (beta) project. {% data reusables.webhoo Key | Type | Description ----|------|------------- `action`|`string` | The action that was performed on the project item. Can be one of `archived`, `converted`, `created`, `edited`, `restored`, `deleted`, or `reordered`. -`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." +`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." `changes`|`object` | The changes to the project item. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/content/get-started/using-github/github-command-palette.md b/content/get-started/using-github/github-command-palette.md index 751f81b7a9..c34ba5f52c 100644 --- a/content/get-started/using-github/github-command-palette.md +++ b/content/get-started/using-github/github-command-palette.md @@ -39,8 +39,8 @@ When you open the command palette, it shows your location at the top left and us {% note %} **Notes:** -- If you are editing Markdown text, open the command palette with Ctrl+Alt+K (Windows and Linux) or Command+Option+K (Mac). -- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." +- If you are editing Markdown text, open the command palette with Ctrl+Alt+K (Windows and Linux) or Command+Option+K (Mac).{% ifversion projects-v2 %} +- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %} {% endnote %} @@ -151,7 +151,7 @@ These commands are available from all scopes. |`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | |`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | |`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | -|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | +|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." | |`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | |`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | diff --git a/content/get-started/using-github/keyboard-shortcuts.md b/content/get-started/using-github/keyboard-shortcuts.md index cf773a630a..514cc154e7 100644 --- a/content/get-started/using-github/keyboard-shortcuts.md +++ b/content/get-started/using-github/keyboard-shortcuts.md @@ -141,7 +141,34 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.| |Click, then Shift and click | Comment on multiple lines of a pull request by clicking a line number, holding Shift, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."| -## Project boards +{% ifversion projects-v2 %} + +## {% data variables.projects.projects_v2_caps %} + +### Navigating a project + +| Keyboard shortcut | Description +|-----------|------------ +|⌘+f (Mac) or Ctrl+f (Windows/Linux) | Focus filter field +|← | Move cell focus to the left +|→ | Move cell focus to the right +|↑ | Move cell focus up +|↓ | Move cell focus down + +### Manipulating a project + +| Keyboard shortcut | Description +|-----------|------------ +|Enter | Toggle edit mode for the focused cell +|Escape | Cancel editing for the focused cell +|⌘+Shift+\ (Mac) or Ctrl+Shift+\ (Windows/Linux) | Open row actions menu +|Shift+Space | Select item +|Space | Open selected item +|e | Archive selected items + +{% endif %} + +## {% data variables.product.prodname_projects_v1_caps %} ### Moving a column diff --git a/content/issues/guides.md b/content/issues/guides.md index a1f73834df..cc1f1221f6 100644 --- a/content/issues/guides.md +++ b/content/issues/guides.md @@ -10,11 +10,11 @@ versions: ghae: '*' ghec: '*' includeGuides: - - /issues/trying-out-the-new-projects-experience/automating-projects - - /issues/trying-out-the-new-projects-experience/creating-a-project - - /issues/trying-out-the-new-projects-experience/customizing-your-project-views - - /issues/trying-out-the-new-projects-experience/quickstart - - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects + - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions + - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project + - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view + - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects + - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects - /issues/tracking-your-work-with-issues/quickstart - /issues/tracking-your-work-with-issues/creating-an-issue - /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests diff --git a/content/issues/index.md b/content/issues/index.md index a6398bee56..9a41b4fc11 100644 --- a/content/issues/index.md +++ b/content/issues/index.md @@ -8,18 +8,19 @@ introLinks: featuredLinks: guides: - /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue - - /issues/trying-out-the-new-projects-experience/quickstart - - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects + - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects + - /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository - /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project guideCards: - - /issues/trying-out-the-new-projects-experience/automating-projects + - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view - /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue - '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}' - - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects + - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions popular: - /issues/tracking-your-work-with-issues/creating-issues/about-issues - - /issues/trying-out-the-new-projects-experience/about-projects + - /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects + - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project - /issues/tracking-your-work-with-issues/creating-issues/about-task-lists - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates - /issues/using-labels-and-milestones-to-track-work/managing-labels @@ -32,8 +33,8 @@ featuredLinks: href: 'https://www.youtube-nocookie.com/embed/HwpVvDURHKw' - title: Issue Forms for open source – Luke Hefson href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY' - videosHeading: GitHub Universe 2021 videos -product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA' + videosHeading: Videos +product_video: '{% ifversion projects-v2 %}https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y{% else %}https://www.youtube-nocookie.com/embed/uiaLWluYJsA{% endif %}' layout: product-landing beta_product: false versions: @@ -43,7 +44,7 @@ versions: ghec: '*' children: - /tracking-your-work-with-issues - - /trying-out-the-new-projects-experience + - /planning-and-tracking-with-projects - /organizing-your-work-with-project-boards - /using-labels-and-milestones-to-track-work - /guides diff --git a/content/issues/organizing-your-work-with-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/index.md index a24fa36cc3..4d078aae54 100644 --- a/content/issues/organizing-your-work-with-project-boards/index.md +++ b/content/issues/organizing-your-work-with-project-boards/index.md @@ -1,12 +1,10 @@ --- -title: Organizing your work with project boards -shortTitle: Project boards -intro: 'Use project boards to manage your work on {% data variables.product.prodname_dotcom %}' +title: 'Organizing your work with {% data variables.product.prodname_projects_v1 %}' +shortTitle: '{% data variables.product.prodname_projects_v1_caps %}' +intro: 'Use {% data variables.product.prodname_projects_v1 %} to manage your work on {% data variables.product.prodname_dotcom %}' +allowTitleToDifferFromFilename: true versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Issues - Projects diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md index 900568a794..26f41444fb 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md @@ -1,30 +1,28 @@ --- -title: About automation for project boards -intro: You can configure automatic workflows to keep the status of project board cards in sync with the associated issues and pull requests. +title: About automation for {% data variables.product.prodname_projects_v1 %} +intro: You can configure automatic workflows to keep the status of {% data variables.projects.projects_v1_board %} cards in sync with the associated issues and pull requests. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards - /articles/about-automation-for-project-boards - /github/managing-your-work-on-github/about-automation-for-project-boards versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Automation for project boards +shortTitle: Automation for {% data variables.product.prodname_projects_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[{% data variables.product.prodname_projects_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." -You can automate actions based on triggering events for project board columns. This eliminates some of the manual tasks in managing a project board. For example, you can configure a "To do" column, where any new issues or pull requests you add to a project board are automatically moved to the configured column. For more information, see "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)." +You can automate actions based on triggering events for {% data variables.projects.projects_v1_board %} columns. This eliminates some of the manual tasks in managing a {% data variables.projects.projects_v1_board %}. For example, you can configure a "To do" column, where any new issues or pull requests you add to a {% data variables.projects.projects_v1_board %} are automatically moved to the configured column. For more information, see "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)." {% data reusables.project-management.use-automated-template %} {% data reusables.project-management.copy-project-boards %} -Project board automation can also help teams develop a shared understanding of a project board's purpose and the team's development process by creating a standard workflow for certain actions. +{% data variables.projects.projects_v1_board_caps %} automation can also help teams develop a shared understanding of a {% data variables.projects.projects_v1_board %}'s purpose and the team's development process by creating a standard workflow for certain actions. {% data reusables.project-management.resync-automation %} @@ -38,10 +36,10 @@ Project board automation can also help teams develop a shared understanding of a ## Project progress tracking -You can track the progress on your project board. Cards in the "To do", "In progress", or "Done" columns count toward the overall project progress. {% data reusables.project-management.project-progress-locations %} +You can track the progress on your {% data variables.projects.projects_v1_board %}. Cards in the "To do", "In progress", or "Done" columns count toward the overall project progress. {% data reusables.project-management.project-progress-locations %} -For more information, see "[Tracking progress on your project board](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)." +For more information, see "[Tracking progress on your {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)." ## Further reading -- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %} -- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %} +- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index 833004a4f8..080500a289 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,55 +1,53 @@ --- -title: About project boards -intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.' +title: About {% data variables.product.prodname_projects_v1 %} +intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards - /articles/about-projects - /articles/about-project-boards - /github/managing-your-work-on-github/about-project-boards versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns. +{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns. -Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %} +{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %} -You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." +You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." Types of project boards: -- **User-owned project boards** can contain issues and pull requests from any personal repository. -- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." -- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories. +- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository. +- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)." +- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories. -## Creating and viewing project boards +## Creating and viewing {% data variables.projects.projects_v1_boards %} -To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board. +To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}. -If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." -The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down. +The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down. -To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)." +To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)." -To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)." +To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)." -If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)." +If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)." -You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way. +You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way. {% data reusables.project-management.project-board-import-with-api %} -## Templates for project boards +## Templates for {% data variables.projects.projects_v1_boards %} -You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured. +You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. You can also choose a template with automation already configured. | Template | Description | | --- | --- | @@ -58,17 +56,17 @@ You can use templates to quickly set up a new project board. When you use a temp | Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status | | Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns | -For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)." +For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." -![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png) +![{% data variables.product.prodname_project_v1 %} with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png) {% data reusables.project-management.copy-project-boards %} ## Further reading -- "[Creating a project board](/articles/creating-a-project-board)" -- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} -- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} -- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" +- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" - "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md index 39e797a668..43a816a1c4 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md @@ -1,18 +1,16 @@ --- -title: Changing project board visibility -intro: 'As an organization owner or project board admin, you can make a project board {% ifversion ghae %}internal{% else %}public{% endif %} or private.' +title: Changing {% data variables.product.prodname_project_v1 %} visibility +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility - /articles/changing-project-board-visibility - /github/managing-your-work-on-github/changing-project-board-visibility versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests shortTitle: Change visibility +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} @@ -20,7 +18,7 @@ shortTitle: Change visibility {% tip %} -**Tip:** When you make your project board {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md index c75fb54ace..23bb9ce219 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md @@ -1,35 +1,33 @@ --- -title: Closing a project board -intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.' +title: Closing a {% data variables.product.prodname_project_v1 %} +intro: 'If you''ve completed all the tasks in a {% data variables.projects.projects_v1_board %} or no longer need to use a {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board - /articles/closing-a-project - /articles/closing-a-project-board - /github/managing-your-work-on-github/closing-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -When you close a project board, any configured workflow automation will pause by default. +When you close a {% data variables.projects.projects_v1_board %}, any configured workflow automation will pause by default. -If you reopen a project 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 "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)." +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 "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." -1. Navigate to the list of project boards in your repository or organization, or owned by your personal account. -2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}. +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" %}. ![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png) 3. Click **Close**. ![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png) ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Deleting a project board](/articles/deleting-a-project-board)" -- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)" -- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)" -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)" +- "[Disabling {% data variables.product.prodname_projects_v1 %} in a repository](/articles/disabling-project-boards-in-a-repository)" +- "[Disabling {% data variables.product.prodname_projects_v1 %} in your organization](/articles/disabling-project-boards-in-your-organization)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md index cccec582e3..bf3817ccec 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md @@ -1,15 +1,12 @@ --- -title: Configuring automation for project boards -intro: You can set up automatic workflows to move issues and pull requests to a project board column when a specified event occurs. +title: Configuring automation for {% data variables.product.prodname_projects_v1 %} +intro: You can set up automatic workflows to move issues and pull requests to a {% data variables.projects.projects_v1_board %} column when a specified event occurs. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards - /articles/configuring-automation-for-project-boards - /github/managing-your-work-on-github/configuring-automation-for-project-boards versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests - Projects @@ -17,10 +14,11 @@ topics: - Project management shortTitle: Configure automation type: how_to +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)." +{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." {% data reusables.project-management.use-automated-template %} @@ -32,7 +30,7 @@ type: how_to {% endtip %} -1. Navigate to the project board you want to automate. +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" %}. ![Edit icon](/assets/images/help/projects/edit-column-button.png) 3. Click **Manage automation**. @@ -44,4 +42,4 @@ type: how_to 6. Click **Update automation**. ## Further reading -- "[About automation for project boards](/articles/about-automation-for-project-boards)" +- "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md index a2d0358259..77942f76dd 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md @@ -1,6 +1,8 @@ --- -title: Copying a project board -intro: You can copy a project board to quickly create a new project. Copying frequently used or highly customized project boards helps standardize your workflow. +title: Copying a {% data variables.product.prodname_project_v1 %} +intro: You can copy a {% data variables.projects.projects_v1_board %} + to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} + helps standardize your workflow. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board - /articles/copying-a-project-board @@ -10,24 +12,25 @@ versions: ghec: '*' topics: - Pull requests +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -Copying a project board allows you to reuse a project board's title, description, and automation configuration. You can copy project boards to eliminate the manual process of creating new project boards for similar workflows. +Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows. -You must have read access to a project board to copy it to a repository or organization where you have write access. +You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access. -When you copy a project board to an organization, the project board's visibility will default to private, with an option to change the visibility. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility/)." +When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)." -A project board's automation is also enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)." +A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)." -1. Navigate to the project board you want to copy. +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**. ![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png) 4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board. ![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png) -5. Optionally, under "Project board name", type the name of the copied project board. +5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}. ![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png) 6. Optionally, under "Description", type a description of the copied project board that other people will see. ![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png) diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md index 92610d66c9..c607acad1f 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md @@ -1,22 +1,20 @@ --- -title: Creating a project board -intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.' +title: Creating a {% data variables.product.prodname_project_v1 %} +intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board - /articles/creating-a-project - /articles/creating-a-project-board - /github/managing-your-work-on-github/creating-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests - Issues - Projects - Project management type: how_to +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} @@ -24,21 +22,23 @@ type: how_to {% data reusables.project-management.copy-project-boards %} -{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." +{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %} +](/articles/linking-a-repository-to-a-project-board)." -Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." +Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." -You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)." +You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." {% data reusables.project-management.project-board-import-with-api %} -## Creating a user-owned project board +## Creating a user-owned {% data variables.projects.projects_v1_board %} {% data reusables.projects.classic-project-creation %} {% data reusables.profile.access_profile %} 2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**. -![Project tab](/assets/images/help/projects/user-projects-tab.png) +![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} @@ -54,13 +54,14 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.edit-project-columns %} -## Creating an organization-wide project board +## Creating an organization-wide {% data variables.projects.projects_v1_board %} {% data reusables.projects.classic-project-creation %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} @@ -76,13 +77,14 @@ You can also configure workflow automations to keep your project board in sync w {% data reusables.project-management.edit-project-columns %} -## Creating a repository project board +## Creating a repository {% data variables.projects.projects_v1_board %} {% 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**. -![Project tab](/assets/images/help/projects/repo-tabs-projects.png) +![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md index 1c13437734..875f1ce7c3 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md @@ -1,28 +1,26 @@ --- -title: Deleting a project board -intro: You can delete an existing project board if you no longer need access to its contents. +title: Deleting a {% data variables.product.prodname_project_v1 %} +intro: You can delete an existing {% data variables.projects.projects_v1_board %} if you no longer need access to its contents. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board - /articles/deleting-a-project - /articles/deleting-a-project-board - /github/managing-your-work-on-github/deleting-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} {% tip %} -**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it. +**Tip**: If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board) instead of deleting it. {% endtip %} -1. Navigate to the project board you want to delete. +1. Navigate to the {% data variables.projects.projects_v1_board %} you want to delete. {% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} 4. Click **Delete project**. @@ -31,6 +29,6 @@ topics: ## Further reading -- "[Closing a project board](/articles/closing-a-project-board)" -- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)" -- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)" +- "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)" +- "[Disabling {% data variables.product.prodname_project_v1_caps %} in a repository](/articles/disabling-project-boards-in-a-repository)" +- "[Disabling {% data variables.product.prodname_project_v1_caps %} in your organization](/articles/disabling-project-boards-in-your-organization)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md index e80b1eec6e..800d88786e 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md @@ -1,6 +1,6 @@ --- -title: Editing a project board -intro: You can edit the title and description of an existing project board. +title: Editing a {% data variables.product.prodname_project_v1 %} +intro: You can edit the title and description of an existing {% data variables.projects.projects_v1_board %}. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board - /articles/editing-a-project @@ -8,29 +8,27 @@ redirect_from: - /articles/editing-a-project-board - /github/managing-your-work-on-github/editing-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} {% tip %} -**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)." +**Tip:** For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)." {% endtip %} -1. Navigate to the project board you want to edit. +1. Navigate to the {% data variables.projects.projects_v1_board %} you want to edit. {% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Modify the project board name and description as needed, then click **Save project**. +4. Modify the {% data variables.projects.projects_v1_board %} name and description as needed, then click **Save project**. ![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png) ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Deleting a project board](/articles/deleting-a-project-board)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md index ada41ccd40..5959e245db 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md @@ -1,12 +1,9 @@ --- -title: Managing project boards -shortTitle: Managing project boards -intro: Learn how to create and manage project boards +title: Managing {% data variables.product.prodname_projects_v1 %} +shortTitle: Managing {% data variables.product.prodname_projects_v1 %} +intro: Learn how to create and manage {% data variables.projects.projects_v1_boards %} versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Issues - Projects @@ -24,6 +21,7 @@ children: - /deleting-a-project-board redirect_from: - /github/managing-your-work-on-github/managing-project-boards +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md index 1c5c663bc8..7e94574247 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md @@ -1,26 +1,24 @@ --- -title: Linking a repository to a project board -intro: You can link a repository to your organization's or personal account's project board. +title: Linking a repository to a {% data variables.product.prodname_project_v1 %} +intro: You can link a repository to your organization's or personal account's {% data variables.projects.projects_v1_board %}. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board - /articles/linking-a-repository-to-a-project-board - /github/managing-your-work-on-github/linking-a-repository-to-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests shortTitle: Link repository to board +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -Anyone with write permissions to a project board can link repositories owned by that organization or personal account to the project board. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned project boards](/articles/permission-levels-for-user-owned-project-boards/)." +Anyone with write permissions to a {% data variables.projects.projects_v1_board %} can link repositories owned by that organization or personal account to the {% data variables.projects.projects_v1_board %}. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned {% data variables.product.prodname_projects_v1 %}](/articles/permission-levels-for-user-owned-project-boards/)." -{% data reusables.project-management.link-repos-to-project-board %} You can add issues and pull requests from any unlinked repositories by typing the issue or pull request URL in a card. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)." +{% data reusables.project-management.link-repos-to-project-board %} You can add issues and pull requests from any unlinked repositories by typing the issue or pull request URL in a card. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)." -1. Navigate to the project board where you want to link a repository. +1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to link a repository. {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} 4. In the left sidebar, click **Linked repositories**. @@ -34,10 +32,10 @@ Anyone with write permissions to a project board can link repositories owned by {% note %} -**Note:** In order to link a repository to your organization or user owned project board the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default). For information on how to enable or disable issues for a repository, see "[Disabling issues for a repository](/github/managing-your-work-on-github/disabling-issues)." +**Note:** In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. That is, the repository has an "Issues" tab (in forked repositories issues are disabled by default). For information on how to enable or disable issues for a repository, see "[Disabling issues for a repository](/github/managing-your-work-on-github/disabling-issues)." {% endnote %} ## Further reading -- "[About projects boards](/articles/about-project-boards)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md index b290d300bc..56046b8806 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md @@ -1,33 +1,31 @@ --- -title: Reopening a closed project board -intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board. +title: Reopening a closed {% data variables.product.prodname_project_v1 %} +intro: You can reopen a closed {% data variables.projects.projects_v1_board %} and restart any workflow automation that was configured for the {% data variables.projects.projects_v1_board %}. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board - /articles/reopening-a-closed-project-board - /github/managing-your-work-on-github/reopening-a-closed-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Reopen project board +shortTitle: Reopen {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -When you close a project board, any workflow automation that was configured for the project board will pause by default. For more information, see "[Closing a project board](/articles/closing-a-project-board)." +When you close a {% data variables.projects.projects_v1_board %}, any workflow automation that was configured for the {% data variables.projects.projects_v1_board %} will pause by default. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)." -When you reopen a project 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. +When 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. -1. Navigate to the project board you want to reopen. +1. Navigate to the {% data variables.projects.projects_v1_board %} you want to reopen. {% data reusables.project-management.click-menu %} -3. Choose whether to sync automation for your project board or reopen your project board without syncing. - - To reopen your project board and sync automation, click **Reopen and sync project**. +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**. ![Select "Reopen and resync project" button](/assets/images/help/projects/reopen-and-sync-project.png) - - To reopen your project board without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**. + - 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**. ![Reopen closed project board drop-down menu](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png) ## Further reading -- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)" +- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)" diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md index 6c67376231..445aa3fb86 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md @@ -1,26 +1,24 @@ --- -title: Adding issues and pull requests to a project board -intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns. +title: Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %} +intro: You can add issues and pull requests to a {% data variables.projects.projects_v1_board %} in the form of cards and triage them into columns. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board - /articles/adding-issues-and-pull-requests-to-a-project - /articles/adding-issues-and-pull-requests-to-a-project-board - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Add issues & PRs to board +shortTitle: Add issues & PRs to {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -You can add issue or pull request cards to your project board by: +You can add issue or pull request cards to your {% data variables.projects.projects_v1_board %} by: - Dragging cards from the **Triage** section in the sidebar. - Typing the issue or pull request URL in a card. -- Searching for issues or pull requests in the project board search sidebar. +- Searching for issues or pull requests in the {% data variables.projects.projects_v1_board %} search sidebar. 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. @@ -28,30 +26,30 @@ You can put a maximum of 2,500 cards into each project column. If a column has r {% 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 project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." +**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 "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." {% endnote %} {% data reusables.project-management.edit-in-project %} -{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." +{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %}, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." -## Adding issues and pull requests to a project board +## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} -1. Navigate to the project board where you want to add issues and pull requests. -2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. +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**. ![Add cards button](/assets/images/help/projects/add-cards-button.png) -3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)." +3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)." ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png) {% tip %} **Tips:** - You can also add an issue or pull request by typing the URL in a card. - - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)." + - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)." {% endtip %} -4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} +4. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} {% tip %} @@ -59,21 +57,21 @@ You can put a maximum of 2,500 cards into each project column. If a column has r {% endtip %} -## Adding issues and pull requests to a project board from the sidebar +## 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" %}**. ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png) -2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to. +2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to. ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png) 3. Type the name of the project in **Filter projects** field. ![Project board search box](/assets/images/help/projects/sidebar-search-project.png) -4. Select one or more project boards where you want to add the issue or pull request. +4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request. ![Selected project board](/assets/images/help/projects/sidebar-select-project.png) -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 project board column you select. +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. ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Editing a project board](/articles/editing-a-project-board)" -- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" +- "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)" diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md index 2cf815d675..c0b1c48945 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md @@ -1,19 +1,17 @@ --- -title: Adding notes to a project board -intro: You can add notes to a project board to serve as task reminders or to add information related to the project board. +title: Adding notes to a {% data variables.product.prodname_project_v1 %} +intro: You can add notes to a {% data variables.projects.projects_v1_board %} to serve as task reminders or to add information related to the {% data variables.projects.projects_v1_board %}. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board - /articles/adding-notes-to-a-project - /articles/adding-notes-to-a-project-board - /github/managing-your-work-on-github/adding-notes-to-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Add notes to board +shortTitle: Add notes to {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} @@ -22,17 +20,17 @@ shortTitle: Add notes to board **Tips:** - You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)." - You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} -- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)." +- Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)." {% endtip %} -When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text. +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. ![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png) -## Adding notes to a project board +## Adding notes to a {% data variables.projects.projects_v1_board %} -1. Navigate to the project board where you want to add notes. +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" %}. ![Plus icon in the column header](/assets/images/help/projects/add-note-button.png) 3. Type your note, then click **Add**. @@ -52,7 +50,7 @@ When you convert a note to an issue, the issue is automatically created using th {% tip %} -**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." +**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." {% endtip %} @@ -60,12 +58,12 @@ When you convert a note to an issue, the issue is automatically created using th {% data reusables.project-management.project-note-more-options %} 3. Click **Convert to issue**. ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png) -4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to. +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. ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png) 5. Optionally, edit the pre-filled issue title, and type an issue body. ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png) 6. Click **Convert to issue**. -7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note. +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. ## Editing and removing a note @@ -78,7 +76,7 @@ When you convert a note to an issue, the issue is automatically created using th ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Creating a project board](/articles/creating-a-project-board)" -- "[Editing a project board](/articles/editing-a-project-board)" -- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" +- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)" +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md index b7d8e6e244..f232d9d14b 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md @@ -1,34 +1,32 @@ --- -title: Archiving cards on a project board -intro: You can archive project board cards to declutter your workflow without losing the historical context of a project. +title: Archiving cards on a {% data variables.product.prodname_project_v1 %} +intro: You can archive {% data variables.projects.projects_v1_board %} cards to declutter your workflow without losing the historical context of a project. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board - /articles/archiving-cards-on-a-project-board - /github/managing-your-work-on-github/archiving-cards-on-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Archive cards on board +shortTitle: Archive cards on {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -Automation in your project board does not apply to archived project board cards. For example, if you close an issue in a project board's archive, the archived card does not automatically move to the "Done" column. When you restore a card from the project board archive, the card will return to the column where it was archived. +Automation in your {% data variables.projects.projects_v1_board %} does not apply to archived {% data variables.projects.projects_v1_board %} cards. For example, if you close an issue in a {% data variables.projects.projects_v1_board %}'s archive, the archived card does not automatically move to the "Done" column. When you restore a card from the {% data variables.projects.projects_v1_board %} archive, the card will return to the column where it was archived. -## Archiving cards on a project board +## Archiving cards on a {% data variables.projects.projects_v1_board %} -1. In a project 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="The horizontal kebab icon" %}. ![List of options for editing a project board card](/assets/images/help/projects/select-archiving-options-project-board-card.png) 2. Click **Archive**. ![Select archive option from menu](/assets/images/help/projects/archive-project-board-card.png) -## Restoring cards on a project board from the sidebar +## 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**. ![Select view archive option from menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png) -3. Above the project board card you want to unarchive, click **Restore**. +3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**. ![Select restore project board card](/assets/images/help/projects/restore-card.png) diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index df592acef0..2d0aa56149 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -1,24 +1,22 @@ --- -title: Filtering cards on a project board -intro: You can filter the cards on a project board to search for specific cards or view a subset of the cards. +title: Filtering cards on a {% data variables.product.prodname_project_v1 %} +intro: You can filter the cards on a {% data variables.projects.projects_v1_board %} to search for specific cards or view a subset of the cards. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board - /articles/filtering-cards-on-a-project-board - /github/managing-your-work-on-github/filtering-cards-on-a-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Filter cards on board +shortTitle: Filter cards on {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} -On a card, you can click any assignee, milestone, or label to filter the project board by that qualifier. To clear the search, you can click the same assignee, milestone, or label again. +On a card, you can click any assignee, milestone, or label to filter the {% data variables.projects.projects_v1_board %} by that qualifier. To clear the search, you can click the same assignee, milestone, or label again. -You can also use the "Filter cards" search bar at the top of each project board to search for cards. You can filter cards using the following search qualifiers in any combination, or by simply typing some text you'd like to search for. +You can also use the "Filter cards" search bar at the top of each {% data variables.projects.projects_v1_board %} to search for cards. You can filter cards using the following search qualifiers in any combination, or by simply typing some text you'd like to search for. - Filter cards by author using `author:USERNAME` - Filter cards by assignee using `assignee:USERNAME` or `no:assignee` @@ -30,9 +28,9 @@ You can also use the "Filter cards" search bar at the top of each project board - Filter cards by type using `type:issue`, `type:pr`, or `type:note` - Filter cards by state and type using `is:open`, `is:closed`, or `is:merged`; and `is:issue`, `is:pr`, or `is:note` - Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` -- Filter cards by repository in an organization-wide project board using `repo:ORGANIZATION/REPOSITORY` +- Filter cards by repository in an organization-wide {% data variables.projects.projects_v1_board %} using `repo:ORGANIZATION/REPOSITORY` -1. Navigate to the project board that contains the cards you want to filter. +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. ![Filter card search bar](/assets/images/help/projects/filter-card-search-bar.png) @@ -44,6 +42,6 @@ You can also use the "Filter cards" search bar at the top of each project board ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)" +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)" diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md index 563070720c..cc5e8fc2e8 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md @@ -1,12 +1,9 @@ --- -title: Tracking progress on your project board -shortTitle: Tracking projects -intro: Learn how to track your work on project boards +title: Tracking progress on your {% data variables.product.prodname_projects_v1 %} +shortTitle: Tracking {% data variables.product.prodname_projects_v1 %} +intro: Learn how to track your work on {% data variables.projects.projects_v1_board %} versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Issues - Projects @@ -18,6 +15,7 @@ children: - /archiving-cards-on-a-project-board redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md index dde14695ee..1d9ce8bb28 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md @@ -1,24 +1,22 @@ --- -title: Tracking progress on your project board -intro: You can see the overall progress of your project in a progress bar. +title: Tracking progress on your {% data variables.product.prodname_project_v1 %} +intro: You can see the overall progress of your {% data variables.projects.projects_v1_board %} in a progress bar. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board - /articles/tracking-progress-on-your-project-board - /github/managing-your-work-on-github/tracking-progress-on-your-project-board versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' + feature: "projects-v1" topics: - Pull requests -shortTitle: Track progress on board +shortTitle: Track progress on {% data variables.product.prodname_project_v1 %} +allowTitleToDifferFromFilename: true --- {% data reusables.projects.project_boards_old %} {% data reusables.project-management.project-progress-locations %} -1. Navigate to the project board where you want to enable or disable project progress tracking. +1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to enable or disable project progress tracking. {% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} 4. Select or deselect **Track project progress**. diff --git a/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md similarity index 94% rename from content/issues/trying-out-the-new-projects-experience/automating-projects.md rename to content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md index 0fb4d7c983..e58ee7f479 100644 --- a/content/issues/trying-out-the-new-projects-experience/automating-projects.md +++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md @@ -1,33 +1,18 @@ --- -title: Automating projects (beta) -intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.' -allowTitleToDifferFromFilename: true +title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions' +shortTitle: 'Automating with Actions' +intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.' miniTocMaxHeadingLevel: 3 versions: - fpt: '*' - ghec: '*' + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/automating-projects type: tutorial topics: - Projects - - Workflows - - Project management +allowTitleToDifferFromFilename: true --- -{% data reusables.projects.projects-beta %} - -{% data reusables.projects.graphql-deprecation %} - -## Introduction - -You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}. - -## Built-in workflows - -{% data reusables.projects.about-workflows %} - -You can enable or disable the built-in workflows for your project. - -{% data reusables.projects.enable-basic-workflow %} ## {% data variables.product.prodname_actions %} workflows @@ -39,11 +24,13 @@ A project can span multiple repositories, but a workflow is specific to a reposi This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)." -For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." +For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." + +You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README. {% note %} -**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access projects (beta). To access projects (beta) you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below. +**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below. {% endnote %} diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md new file mode 100644 index 0000000000..0feea7fef0 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md @@ -0,0 +1,15 @@ +--- +title: 'Automating your {% data variables.projects.project_v2 %}' +shortTitle: 'Automating {% data variables.projects.projects_v2 %}' +intro: 'Learn how to use the built-in workflows, {% data variables.product.prodname_actions %}, and the API to automate your projects.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /using-the-built-in-automations + - /using-the-api-to-manage-projects + - /automating-projects-using-actions +allowTitleToDifferFromFilename: true +--- diff --git a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md similarity index 95% rename from content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md rename to content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md index 590686dd2a..3f9bead44b 100644 --- a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md +++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md @@ -1,22 +1,22 @@ --- -title: Using the API to manage projects (beta) -intro: You can use the GraphQL API to find information about projects and to update projects. -versions: - fpt: '*' - ghec: '*' +title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}' +shortTitle: 'Automating with the API' +intro: 'You can use the GraphQL API to automate your projects.' miniTocMaxHeadingLevel: 3 -allowTitleToDifferFromFilename: true -type: how_to +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects +type: tutorial topics: - Projects +allowTitleToDifferFromFilename: true --- +This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." For a full list of the available data types, see "[Reference](/graphql/reference)." + {% data reusables.projects.graphql-deprecation %} -This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)." - -{% data reusables.projects.projects-beta %} - ## Authentication {% curl %} @@ -714,3 +714,7 @@ gh api graphql -f query=' }' ``` {% endcli %} + +## Using webhooks + +You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.product_name %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." To learn more about the `projects_v2_item` webhook event, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item)." \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md new file mode 100644 index 0000000000..06e7274342 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md @@ -0,0 +1,23 @@ +--- +title: 'Using the built-in automations' +shortTitle: 'Using built-in automations' +intro: 'You can use built-in workflows to automate your projects.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +{% note %} + +**Note:** Built-in workflows are available as part of a limited beta. + +{% endnote %} + +{% data reusables.projects.about-workflows %} + +You can enable or disable the built-in workflows for your project. + +{% data reusables.projects.enable-basic-workflow %} diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md new file mode 100644 index 0000000000..e1e5d6f8a0 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md @@ -0,0 +1,39 @@ +--- +title: 'Creating a {% data variables.projects.project_v2 %}' +intro: 'Learn how to create an organization or user project.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/creating-a-project +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +{% data variables.product.prodname_projects_v2 %} are an adaptable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you note down. You can add custom fields and create views for specific purposes. + +## Creating a project + +### Creating an organization project + +Organization projects can track issues and pull requests from the organization's repositories. + +{% data reusables.projects.create-project %} + +### Creating a user project + +User projects can track issues and pull requests from the repositories owned by your personal account. + +{% data reusables.projects.create-user-project %} + +## Updating your project description and README + +{% data reusables.projects.project-description %} + +## Further reading + +- "[Adding your project to a repository](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)" +- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)" +- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/content/issues/planning-and-tracking-with-projects/creating-projects/index.md new file mode 100644 index 0000000000..5d8b5ba9cd --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/creating-projects/index.md @@ -0,0 +1,15 @@ +--- +title: 'Creating {% data variables.projects.projects_v2 %}' +shortTitle: 'Creating {% data variables.projects.projects_v2 %}' +intro: 'Learn about creating projects and migrating your {% data variables.projects.projects_v1_boards %}.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /creating-a-project + - /migrating-from-projects-classic +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md similarity index 66% rename from content/issues/trying-out-the-new-projects-experience/migrating-your-project.md rename to content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md index a2e2c20537..d36dc4a14f 100644 --- a/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md +++ b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md @@ -1,23 +1,24 @@ --- -title: Migrating your project to Projects (beta) -intro: You can migrate your projects from the old projects experience to Projects (beta). -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 +title: 'Migrating from {% data variables.product.prodname_projects_v1 %}' +intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.' +miniTocMaxHeadingLevel: 3 versions: - fpt: '*' - ghec: '*' + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/migrating-your-project +type: tutorial topics: - Projects - - Organizations +allowTitleToDifferFromFilename: true --- + {% note %} **Notes:** -- Projects (beta) is currently in public beta and subject to change. - If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated. -- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#showing-and-hiding-fields)." +- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)." - Automation will not be migrated. - Triage, archive, and activity will not be migrated. - After migration, the new migrated project and old project will not be kept in sync. @@ -26,7 +27,7 @@ topics: ## About project migration -You can migrate your project boards to the all new projects (beta) experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." +You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." ## Migrating an organization project board @@ -52,7 +53,7 @@ You can migrate your project boards to the all new projects (beta) experience an {% note %} -**Note:** Projects (beta) does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository. +**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository. {% endnote %} @@ -62,4 +63,4 @@ You can migrate your project boards to the all new projects (beta) experience an ![Project tab](/assets/images/help/projects/repo-tabs-projects.png) 1. Click **Projects (classic)**. ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png) -{% data reusables.projects.migrate-project-steps %} +{% data reusables.projects.migrate-project-steps %} \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md new file mode 100644 index 0000000000..c052704e53 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md @@ -0,0 +1,114 @@ +--- +title: 'Customizing a view' +intro: 'Display the information you need by changing the layout, grouping, sorting in your project.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/customizing-your-project-views +type: tutorial +topics: + - Projects +--- + + +## Changing the project layout + +You can view your project as a table or as a board. + +{% data reusables.projects.open-view-menu %} +1. Under "Layout", click either **Table** or **Board**. + ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) + + + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout." + +## Showing and hiding fields + +You can show or hide a specific field. + +{% data reusables.projects.open-view-menu %} +1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields. + ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) +1. Select or deselect the fields you want to show or hide. + ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png) + +You can also hide individual fields in table view. + +1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. + ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png) +1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**. + ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png) + +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. + +## Reordering fields + +In table layout, you can change the order of fields. + +1. Click the field header. + ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png) +2. While continuing to click, drag the field to the required location. + +## Reordering rows + +In table layout, you can change the order of rows. + +1. Click the number at the start of the row. + ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png) +2. While continuing to click, drag the row to the required location. + +## Sorting by field values + +In table layout, you can sort items by a field value. + +{% note %} + +**Note:** When a table is sorted, you cannot manually reorder rows. + +{% endnote %} + +{% data reusables.projects.open-view-menu %} +1. Click **Sort**. + ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png) +1. Click the field you want to sort by. + ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png) +2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}. + ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png) +3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. + ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by." + +## Grouping by field values in table layout + +In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group. + +{% note %} + +**Note:** You cannot group by title, labels, reviewers, or linked pull requests. + +{% endnote %} + +{% data reusables.projects.open-view-menu %} +1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. + ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) +1. Click the field you want to group by. + ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) +2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list. + ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by." + +## Setting the column field in board layout + +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**. + ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png) +1. Click the field you want to use. + ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by." \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md new file mode 100644 index 0000000000..64b3ecd972 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md @@ -0,0 +1,31 @@ +--- +title: 'Filtering {% data variables.projects.projects_v2 %}' +intro: "Use filters to choose which items appear in your project's views." +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/filtering-projects +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +You can customize 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 "[Customizing your project views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." + +To filter a project, 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. + +Using multiple filters will act as a logical AND filter. For example, `label:bug status:"In progress"` will return items with the `bug` label with the "In progress" status. {% data variables.product.prodname_projects_v2 %} does not currently support logical OR filters across multiple fields. + +The same filters are available for charts you create using insights for {% data variables.product.prodname_projects_v2 %}, allowing you to filter the data used to create your charts. For more information, see "[Using insights with projects](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)." + +## Filtering items + +Click {% octicon "filter" aria-label="the filter icon" %} at the top of the table to show the "Filter by keyword or by field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear. + +{% data reusables.projects.projects-filters %} + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Filter by." + +In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again. \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md new file mode 100644 index 0000000000..677d2c49a1 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md @@ -0,0 +1,16 @@ +--- +title: 'Customizing views in your {% data variables.projects.project_v2 %}' +shortTitle: 'Customizing views' +intro: 'You can create multiple views to look at your project from different angles, deciding which items to show and how to present them.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /customizing-a-view + - /filtering-projects + - /managing-your-views +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md new file mode 100644 index 0000000000..d6e908bd48 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md @@ -0,0 +1,73 @@ +--- +title: 'Managing your views' +intro: 'Learn how to create, save, and manage your project views.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + + +## Creating a project view + +Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. + +For example, you can have: +- A view that shows all items not yet started (filter on "Status"). +- A view that shows the workload for each team (group by a custom "Team" field). +- A view that shows the items with the earliest target ship date (sort by a date field). + +To add a new view: + +{% data reusables.projects.new-view %} + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "New view." + +The new view is automatically saved. + +## Duplicating a view + +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**. + ![Screenshot showing the duplicate menu item](/assets/images/help/projects-v2/duplicate-view.png) + +## Saving changes to a view + +When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. + +![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png) + +If you don't want to save the changes, you can ignore this indicator. No one else will see your changes. + +{% data reusables.projects.save-view %} + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Save view." + +## Reordering saved views + +To change the order of the tabs that contain your saved views, click and drag a tab to a new location. The new tab order is automatically saved. + +## Renaming a saved view + +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**. + ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png) +1. Type the new name for your view. +1. To save your changes, press Return. + +## Deleting a saved view + +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**. + ![Screenshot showing the rename delete item](/assets/images/help/projects-v2/delete-view.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Delete view." \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/index.md b/content/issues/planning-and-tracking-with-projects/index.md new file mode 100644 index 0000000000..b1ab3efe4b --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/index.md @@ -0,0 +1,21 @@ +--- +title: 'Planning and tracking with {% data variables.product.prodname_projects_v2 %}' +shortTitle: '{% data variables.product.prodname_projects_v2 %}' +intro: 'Build adaptable projects to track your work on {% data variables.product.company_short %}.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /learning-about-projects + - /creating-projects + - /managing-items-in-your-project + - /understanding-field-types + - /customizing-views-in-your-project + - /automating-your-project + - /viewing-insights-from-your-project + - /managing-your-project +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md new file mode 100644 index 0000000000..97f909323a --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md @@ -0,0 +1,49 @@ +--- +title: 'About {% data variables.product.prodname_projects_v2 %}' +intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.' +allowTitleToDifferFromFilename: true +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/about-projects +type: overview +topics: + - Projects +--- + +## About {% data variables.product.prodname_projects_v2 %} + +A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes. + +### Staying up-to-date + +Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups. + +### Adding metadata to your tasks + +You can use custom fields to add metadata to your tasks and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields: + +- A date field to track target ship dates. +- A number field to track the complexity of a task. +- A single select field to track whether a task is Low, Medium, or High priority. +- A text field to add a quick note. +- An iteration field to plan work week-by-week, including support for breaks. + +### Viewing your project from different perspectives + +Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options. + +You can view your project as a high density table layout: + +![Project table](/assets/images/help/issues/projects_table.png) + +Or as a board: + +![Project board](/assets/images/help/issues/projects_board.png) + +To help you focus on specific aspects of your project, you can group, sort, or filter items: + +![Project view](/assets/images/help/issues/project_view.png) + +For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." diff --git a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md similarity index 63% rename from content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md rename to content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index 042b769958..7cb88aab8c 100644 --- a/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md +++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,11 +1,12 @@ --- -title: Best practices for managing projects (beta) -intro: 'Learn tips for managing your projects on {% data variables.product.company_short %}.' +title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' +intro: 'Learn tips for managing your projects.' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: - fpt: '*' - ghec: '*' + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects type: overview topics: - Projects @@ -13,9 +14,7 @@ topics: - Project management --- -{% data reusables.projects.projects-beta %} - -You can use projects to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about projects, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)." +You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." ## Break down large issues into smaller issues @@ -39,7 +38,7 @@ For example: Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. -For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#updating-your-project-description-and-readme)." +For more information, see "[Creating a {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." ## Use views @@ -51,32 +50,32 @@ For example: - Group by a custom priority field to monitor the volume of high priority items - Sort by a custom date field to view the items with the earliest target ship date -For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." +For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." ## Have a single source of truth To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location. -{% data variables.product.company_short %} projects automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project. +{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project. ## Use automation You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date. -Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." +{% data variables.product.prodname_projects_v2 %} offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review." -- For an example workflow, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)." -- For more information about the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." +- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." +- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." - For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)." ## Use different field types Take advantage of the various field types to meet your needs. -Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)." +Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value. -For more information about the different field types, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)." +For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md new file mode 100644 index 0000000000..1f09f8557b --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md @@ -0,0 +1,15 @@ +--- +title: 'Learning about {% data variables.product.prodname_projects_v2 %}' +intro: 'Learn about {% data variables.product.prodname_projects_v2 %} and how to make the very best of this powerful tool.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /about-projects + - /quickstart-for-projects + - /best-practices-for-projects +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md new file mode 100644 index 0000000000..89abba3ca8 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md @@ -0,0 +1,167 @@ +--- +title: 'Quickstart for {% data variables.product.prodname_projects_v2 %}' +intro: 'Experience the speed, flexibility, and customization of {% data variables.product.prodname_projects_v2 %} by creating a project in this interactive guide.' +allowTitleToDifferFromFilename: true +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/quickstart +type: quick_start +topics: + - Projects +--- + +## Introduction + +This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators. + +## Prerequisites + +You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." + +In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)." + +## Creating a project + +First, create an organization project or a user project. + +### Creating an organization project + +{% data reusables.projects.create-project %} + +### Creating a user project + +{% data reusables.projects.create-user-project %} + +## Setting your project description and README + +{% data reusables.projects.project-description %} + +## Adding issues to your project + +Next, add a few issues to your project. + +{% data reusables.projects.add-item-via-paste %} + +Repeat the above steps a few times to add multiple issues to your project. + +For more information and other ways to add issues to your project, or about other items you can add to your project, see "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)." + +## Adding draft issues to your project + +Next, add a draft issue to your project. + +{% data reusables.projects.add-draft-issue %} + +## Adding an iteration field + +Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks. + +{% data reusables.projects.new-field %} +1. Select **Iteration** + ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) +3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**. + ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) +4. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) + +## Creating a field to track priority + +Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`. + +{% data reusables.projects.new-field %} +1. Select **Single select** + ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) +1. Below "Options", type the first option, "High". + ![Screenshot showing the single select option](/assets/images/help/projects-v2/priority-example.png) +1. To add additional fields, for "Medium" and "Low", click **Add option**. +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) + +Specify a priority for all issues in your project. + +![Example priorities](/assets/images/help/projects/priority_example.png) + +## Grouping issues by priority + +Next, group all of the items in your project by priority to make it easier to focus on the high priority items. + +{% data reusables.projects.open-view-menu %} +1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. + ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) +1. Click **Priority**. + ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) + +Now, move issues between groups to change their priority. + +1. Choose an issue. +2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group. + +![Move issue between groups](/assets/images/help/projects/move_between_group.gif) + +## Saving the priority view + +When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority. + +{% data reusables.projects.save-view %} + +You can share the URL with your team to keep everyone aligned on the project priorities. + +When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified. + +## Adding a board layout + +To view the progress of your project's issues, you can switch to board layout. + +The board layout is based on the status field, so specify a status for each issue in your project. + +![Example status](/assets/images/help/projects/status_example.png) + +Then, create a new view. + +{% data reusables.projects.new-view %} + +Next, switch to board layout. + +{% data reusables.projects.open-view-menu %} +1. Under "Layout", click **Board**. + ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) + +![Example priorities](/assets/images/help/projects/example_board.png) + +When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future. + +{% data reusables.projects.save-view %} + +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**. + ![Screenshot showing the rename menu item](/assets/images/help/projects-v2/rename-view.png) +1. Type the new name for your view. +1. To save changes, press Return. + +![Example priorities](/assets/images/help/projects/project-view-switch.gif) + +## Configure built-in automation + +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. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. + ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) +1. Under **Default workflows**, click **Item added to project**. + ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) +1. Next to **When**, ensure that both `issues` and `pull requests` are selected. + ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) +1. Next to **Set**, select **Status:Todo**. + ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) +1. Click the **Disabled** toggle to enable the workflow. + ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) + +## Further reading + +- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)" +- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md new file mode 100644 index 0000000000..788796e820 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -0,0 +1,86 @@ +--- +title: 'Adding items to your {% data variables.projects.project_v2 %}' +shortTitle: 'Adding items' +intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' +miniTocMaxHeadingLevel: 4 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +Your project can track draft issues, issues, and pull requests. + +{% note %} + +**Note:** A project can contain a maximum of 1,200 items and 10,000 archived items. + +{% endnote %} + +### Adding issues and pull requests to a project + +#### Pasting the URL of an issue or pull request + +{% data reusables.projects.add-item-via-paste %} + +#### Searching for an issue or pull request + +{% data reusables.projects.add-item-bottom-row %} +2. Enter #. +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. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png) +4. Select the issue or pull request. You can type part of the title to narrow down your options. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png) + +#### Bulk adding issues and pull requests + +1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. + ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png) +1. Click **Add item from repository**. + ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png) +{% data reusables.projects.bulk-add %} + +#### Adding multiple issues or pull requests from a repository + +1. On {% data variables.product.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project. +{% data reusables.repositories.sidebar-issue-pr %} +1. To the left of each issue title, select the issues that you want to add to your project. + ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png) +1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png) +1. Above the list of issues or pull requests, click **Projects**. + ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png) +1. Click the projects you want to add the selected issues or pull requests to. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/projects-v2/issue-index-select-project.png) + +#### Assigning a project from within an issue or pull request + +1. Navigate to the issue or pull request that you want to add to a project. +2. In the side bar, click **Projects**. + ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png) +3. Select the project that you want to add the issue or pull request to. + ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png) +4. Optionally, populate the custom fields. + ![Project sidebar](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) + +#### Using the command palette to add an issue or pull request + +1. {% data reusables.projects.open-command-palette %} +1. Start typing "Add items" and press Return. +{% data reusables.projects.bulk-add %} + +### Creating draft issues + +Draft issues are useful to quickly capture ideas. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project. + +{% data reusables.projects.add-draft-issue %} + +Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)." + +{% note %} + +**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue. + +{% endnote %} \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md new file mode 100644 index 0000000000..10811dd4a7 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -0,0 +1,48 @@ +--- +title: 'Archiving items from your {% data variables.projects.project_v2 %}' +shortTitle: 'Archiving items' +intro: 'You can archive items, keeping them available to restore, or permanently delete them.' +miniTocMaxHeadingLevel: 2 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +## Archiving items + +You can archive an item to keep the context about the item in the project but remove it from the project views. + +{% data reusables.projects.select-an-item %} +{% data reusables.projects.open-item-menu %} +1. Click **Archive**. + ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png) +1. When prompted, confirm your choice by clicking **Archive**. + ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png) + +## Restoring archived items + +1. Navigate to your project. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. + ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png) +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 "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png) +1. To the left of each item title, select the items you would like to restore. + ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png) +1. To restore the selected items, above the list of items, click **Restore**. + ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png) + +## Deleting items + +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**. + ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) +1. When prompted, confirm your choice by clicking **Delete**. + ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md new file mode 100644 index 0000000000..189913d052 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md @@ -0,0 +1,33 @@ +--- +title: 'Converting draft issues to issues' +shortTitle: 'Converting draft issues' +intro: 'Learn how to convert draft issues into issues.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +## 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. + ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-table.png) +2. Select **Convert to issue**. + ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. Select the repository that you want to add the issue to. + ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) + +## 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. + ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-board.png) +2. Select **Convert to issue**. + ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. Select the repository that you want to add the issue to. + ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) + +## Further reading + +- "[Creating draft issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)" \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md new file mode 100644 index 0000000000..1269334f9f --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md @@ -0,0 +1,16 @@ +--- +title: 'Managing items in your {% data variables.projects.project_v2 %}' +shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}' +intro: 'Learn how to add and manage issues, pull requests, and draft issues.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /adding-items-to-your-project + - /converting-draft-issues-to-issues + - /archiving-items-from-your-project +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md new file mode 100644 index 0000000000..5627189643 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md @@ -0,0 +1,26 @@ +--- +title: 'Adding your {% data variables.projects.project_v2 %} to a repository' +shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo' +intro: 'You can add your {% data variables.projects.project_v2 %} to a repository to make it accessible from that repository.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +You can list relevant projects in a repository. You can only list projects that are owned by the same user or organization that owns the repository. + +In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[Managing access to your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." + +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**. + ![Screenshot showing projects tab in a repository](/assets/images/help/projects-v2/repo-tab.png) +1. Click **Add project**. + ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo-button.png) +1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository. + ![Screenshot showing searching for a project](/assets/images/help/projects-v2/add-to-repo-search.png) +1. Click on a project to list it in your repository. + ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo.png) \ No newline at end of file diff --git a/content/issues/trying-out-the-new-projects-experience/managing-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md similarity index 76% rename from content/issues/trying-out-the-new-projects-experience/managing-projects.md rename to content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md index 6389ae9f65..607acea24b 100644 --- a/content/issues/trying-out-the-new-projects-experience/managing-projects.md +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md @@ -1,16 +1,19 @@ --- -title: Managing projects (beta) -intro: 'You can close and re-open projects, or you can permanently delete projects.' -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 +title: 'Closing and deleting your {% data variables.projects.projects_v2 %}' +shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}' +intro: 'Learn about closing, re-opening, and permanently deleting a {% data variables.projects.project_v2 %}.' +miniTocMaxHeadingLevel: 3 versions: - fpt: '*' - ghec: '*' + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/managing-projects +type: tutorial topics: - Projects - - Organizations +allowTitleToDifferFromFilename: true --- + ## Deleting a project You can delete a project to permanently remove it. diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md new file mode 100644 index 0000000000..7d3f535971 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md @@ -0,0 +1,15 @@ +--- +title: 'Managing your {% data variables.projects.project_v2 %}' +intro: 'Learn how to manage your projects and control visibility and access.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /managing-visibility-of-your-projects + - /managing-access-to-your-projects + - /closing-and-deleting-your-projects + - /adding-your-project-to-a-repository +allowTitleToDifferFromFilename: true +--- diff --git a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md similarity index 64% rename from content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md rename to content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md index c0e785f37e..275399fd5e 100644 --- a/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md @@ -1,17 +1,18 @@ --- -title: Managing access to projects (beta) -intro: 'You can control who can view, edit, or manage your projects.' -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 +title: 'Managing access to your {% data variables.projects.projects_v2 %}' +shortTitle: 'Managing {% data variables.projects.project_v2 %} access' +intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.' +miniTocMaxHeadingLevel: 3 versions: - fpt: '*' - ghec: '*' + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/managing-access-to-projects +type: tutorial topics: - Projects - - Organizations +allowTitleToDifferFromFilename: true --- -{% data reusables.projects.projects-beta %} ## About project access @@ -29,7 +30,9 @@ The default base role is `write`, meaning that everyone in the organization can {% data reusables.projects.project-settings %} 1. Click **Manage access**. + ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) 2. Under **Base role**, select the default role. + ![Screenshot showing the base role menu](/assets/images/help/projects-v2/base-role.png) - **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. @@ -43,22 +46,31 @@ You can only invite an individual user to collaborate on your organization-level {% data reusables.projects.project-settings %} 1. Click **Manage access**. + ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) 2. Under **Invite collaborators**, search for the team or individual user that you want to invite. + ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) 3. Select the role for the collaborator. + ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) - **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**. + ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) ### Managing access of an existing collaborator on your project {% data reusables.projects.project-settings %} 1. Click **Manage access**. + ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) 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. + ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s). +1. Edit the role for the collaborator(s). + ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) +1. Optionally, click **Remove** to remove the collaborator(s). + ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) ## Managing access for user-level projects @@ -72,19 +84,28 @@ This only affects collaborators for your project, not for repositories in your p {% data reusables.projects.project-settings %} 1. Click **Manage access**. + ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) 2. Under **Invite collaborators**, search for the user that you want to invite. + ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) 3. Select the role for the collaborator. + ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) - **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**. + ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) ### Managing access of an existing collaborator on your project {% data reusables.projects.project-settings %} 1. Click **Manage access**. + ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) 1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify. - You can use the **Role** drop-down menu to filter the access list. + You can use the **Type** and **Role** drop-down menus to filter the access list. + ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s). +1. Edit the role for the collaborator(s). + ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) +1. Optionally, click **Remove** to remove the collaborator(s). + ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md new file mode 100644 index 0000000000..5d8c6bd7ab --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md @@ -0,0 +1,41 @@ +--- +title: 'Managing visibility of your {% data variables.projects.projects_v2 %}' +shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility' +intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects +type: tutorial +topics: + - Projects +allowTitleToDifferFromFilename: true +permissions: 'Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.' +--- + +## About project visibility + +Projects can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project. + +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 with hidden item](/assets/images/help/projects/hidden-items.png) + +Project admins and organization owners can control project visibility. Organization owners can restrict the ability to change project visibility to just organization owners. + +In public and private projects, insights are only visible to users with write permissions for the project. + +In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI. + +Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." + +## Changing project visibility + +{% data reusables.projects.project-settings %} +1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**. + ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png) + +## Further reading + +- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md new file mode 100644 index 0000000000..8c5304297d --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md @@ -0,0 +1,23 @@ +--- +title: 'About date fields' +shortTitle: 'About date fields' +intro: 'You can create custom date fields that can be set by typing a date or using a calendar.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +You can filter for date values using the `YYYY-MM-DD` format, for example: `date:2022-07-01`. You can also use operators, such as `>`, `>=`, `<`, `<=`, and `..`. For example, `date:>2022-07-01` and `date:2022-07-01..2022-07-31`. You can also provide `@today` to represent the current day in your filter. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + +## Adding a date field + +{% data reusables.projects.new-field %} +1. Select **Date** + ![Screenshot showing the date option](/assets/images/help/projects-v2/new-field-date.png) +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md new file mode 100644 index 0000000000..5d9587881c --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md @@ -0,0 +1,76 @@ +--- +title: 'About iteration fields' +shortTitle: 'About iteration fields' +intro: 'You can create iterations to plan upcoming work and group items.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/managing-iterations +type: tutorial +topics: + - Projects +--- + +You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to focus on a single iteration, and sort by iteration. + +You can filter for iterations by specifying the iteration name or `@current` for the current iteration, `@previous` for the previous iteration, or `@next` for the next iteration. You can also use operators such as `>`, `>=`, `<`, `<=`, and `..`. For example, `iteration:>"Iteration 4"` and `iteration:<@current`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + +When you first create an iteration field, three iterations are automatically created. You can add additional iterations and make other changes on your project's settings page. + +![Screenshot showing the settings for an iteration field](/assets/images/help/issues/iterations-example.png) + +## Adding an iteration field + +{% data reusables.projects.new-field %} +1. Select **Iteration** + ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) +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. + ![Screenshot showing the iteration start date](/assets/images/help/projects-v2/iteration-field-starts.png) +3. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**. + ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) +4. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." + +## Adding new iterations + +{% data reusables.projects.project-settings %} +1. Click the name of the iteration field you want to adjust. + ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) +1. To add a new iteration of the same duration, click **Add iteration**. + ![Screenshot the "add iteration" button](/assets/images/help/projects-v2/add-iteration.png) +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**. + ![Screenshot the add iteration options form](/assets/images/help/projects-v2/add-iteration-options.png) +1. Click **Save changes**. + ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) + +## 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**. + +{% data reusables.projects.project-settings %} +1. Click the name of the iteration field you want to adjust. + ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) +1. To change the name of an iteration, click on the name and start typing. + ![Screenshot an title field to rename an iteration](/assets/images/help/projects-v2/iteration-rename.png) +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**. + ![Screenshot showing iteration dates](/assets/images/help/projects-v2/iteration-date.png) +1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}. + ![Screenshot the delete button](/assets/images/help/projects-v2/iteration-delete.png) +2. Click **Save changes**. + ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) + +## Inserting a break + +You can insert breaks into your iterations to communicate when you are taking time away from scheduled work. The duration of a new break defaults to the length of the most recently created iteration. + +{% data reusables.projects.project-settings %} +1. Click the name of the iteration field you want to adjust. + ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) +2. On the dividing line above an iteration and to the right, click **Insert break**. + ![Screenshot showing location of "Insert break" button](/assets/images/help/issues/iteration-insert-break.png) +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**. + ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md new file mode 100644 index 0000000000..b5e1d38cdc --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md @@ -0,0 +1,40 @@ +--- +title: 'About single select fields' +shortTitle: 'About single select fields' +intro: 'You can create single select fields with defined options that can be selected from a dropdown menu.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +You can filter by your single select fields by specifying the option, for example: `fieldname:option`. You can filter for multiple values by providing a comma-separated list of options, for example: `fieldname:option,option`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + +Single select fields can contain up to 50 options. + +## Adding a single select field + +{% data reusables.projects.new-field %} +1. Select **Single select** + ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) +1. Below "Options", type the first option. + ![Screenshot showing the single select option](/assets/images/help/projects-v2/single-select-create-with-options.png) + - To add additional options, click **Add option**. +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." + +## Editing a single select field + +{% data reusables.projects.project-settings %} +1. Click the name of the single select field you want to adjust. + ![Screenshot showing an single select field](/assets/images/help/projects-v2/select-single-select.png) +1. Edit existing options or click **Add option**. + ![Screenshot showing single select options](/assets/images/help/projects-v2/single-select-edit-options.png) +1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}. + ![Screenshot showing delete button](/assets/images/help/projects-v2/single-select-delete.png) +1. Click **Save options**. + ![Screenshot showing save button](/assets/images/help/projects-v2/save-options.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md new file mode 100644 index 0000000000..e2374912d7 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md @@ -0,0 +1,37 @@ +--- +title: 'About text and number fields' +shortTitle: 'About text and number fields' +intro: 'You can add custom text and number fields to your project.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +You can use text fields to include notes or any other freeform text in your project. + +Text fields can be used in filters, for example: `field:"exact text"`. Text fields and item titles will also be used if you filter for text without specifying a field. + +Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and `..` range queries to filter by a number field. For example: `field:5..15` or `field:>=20`. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + +## Adding a text field + +{% data reusables.projects.new-field %} +1. Select **Text** + ![Screenshot showing the text option](/assets/images/help/projects-v2/new-field-text.png) +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) + +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** + ![Screenshot showing the number option](/assets/images/help/projects-v2/new-field-number.png) +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md new file mode 100644 index 0000000000..db07ef00e0 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md @@ -0,0 +1,18 @@ +--- +title: 'Deleting fields' +intro: 'Learn how to delete a field from your {% data variables.projects.project_v2 %}.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +{% data reusables.projects.project-settings %} +1. Click the name of the field you want to delete. + ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) +1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. + ![Screenshot showing field name](/assets/images/help/projects-v2/field-options.png) +1. Click **Delete field**. + ![Screenshot showing field name](/assets/images/help/projects-v2/delete-field.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md new file mode 100644 index 0000000000..a36c492147 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md @@ -0,0 +1,19 @@ +--- +title: 'Understanding field types' +shortTitle: 'Understanding field types' +intro: 'Learn about the different custom field types, how to add custom fields to your project, and how to manage custom fields.' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +children: + - /about-text-and-number-fields + - /about-date-fields + - /about-single-select-fields + - /about-iteration-fields + - /renaming-fields + - /deleting-fields +allowTitleToDifferFromFilename: true +--- + diff --git a/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md new file mode 100644 index 0000000000..e5d9dcee5e --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md @@ -0,0 +1,17 @@ +--- +title: 'Renaming fields' +intro: 'Learn about renaming existing fields in your {% data variables.projects.project_v2 %}.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +topics: + - Projects +--- + +{% data reusables.projects.project-settings %} +1. Click the name of the field you want to rename. + ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) +1. Under "Field name", type the new name for the field. + ![Screenshot showing field name](/assets/images/help/projects-v2/field-rename.png) +1. To save changes, press Return. \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md new file mode 100644 index 0000000000..eb6a3aa961 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md @@ -0,0 +1,51 @@ +--- +title: 'About insights for {% data variables.product.prodname_projects_v2 %}' +intro: "You can view and customize charts that are built from your project's data." +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +redirect_from: + - /issues/trying-out-the-new-projects-experience/using-insights-with-projects +type: tutorial +product: '{% data reusables.gated-features.historical-insights-for-projects %}' +topics: + - Projects +allowTitleToDifferFromFilename: true +--- + +{% ifversion fpt %} + +{% note %} + +**Note:** Historical charts are currently available as a feature preview for organizations using {% data variables.product.prodname_team %} and are generally available for organizations using {% data variables.product.prodname_ghe_cloud %}. + +{% endnote %} + +{% endif %} + + You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project. You can generate two types of chart: current charts and historical charts. + + ### About current charts + +You can create current charts to visualize your project items. For example, you can create charts to show how many items are assigned to each individual, or how many issues are assigned to each upcoming iteration. + +You can also use filters to manipulate the data used to build your chart. For example, you can create a chart showing how much upcoming work you have, but limit those results to particular labels or assignees. For more information, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + + ![Screenshot showing an stacked column chart showing item types for each iteration](/assets/images/help/issues/column-chart-example.png) + +For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)." + + ### About historical charts + + Historical charts are time-based charts that allow you to view your project's trends and progress. You can view the number of items, grouped by status and other fields, over time. + + The default "Burn up" chart shows item status over time, allowing you to visualize progress and spot patterns over time. + +![Screenshot showing an example of the default burn up chart for the current iteration](/assets/images/help/issues/burnup-example.png) + + To create a historical chart, set your chart's X-axis to "Time." For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)" and "[Configuring charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)." + +## Further reading + +- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" +- "[Disabling insights for {% data variables.product.prodname_projects_v2 %} in your organization](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)" \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md new file mode 100644 index 0000000000..4a629ecca5 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md @@ -0,0 +1,37 @@ +--- +title: 'Configuring charts' +intro: 'Learn how to configure your charts and filter data from your project.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +product: '{% data reusables.gated-features.historical-insights-for-projects %}' +topics: + - Projects +--- + +{% ifversion fpt %} + +{% note %} + +**Note:** Historical charts are currently available as a feature preview. + +{% endnote %} + +{% endif %} + +{% data reusables.projects.access-insights %} +1. In the menu on the left, click on the chart you would like to configure. + ![Screenshot showing selecting a custom chart](/assets/images/help/projects-v2/insights-select-a-chart.png) +1. On the right side of the page, click **Configure**. A panel will open on the right. + ![Screenshot showing the configure button](/assets/images/help/projects-v2/insights-configure.png) +1. To change the type of chart, select the **Layout** dropdown and click on the chart type you want to use. + ![Screenshot showing selecting a chart layout](/assets/images/help/projects-v2/insights-layout.png) +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. + ![Screenshot showing selecting what to display on the x axis](/assets/images/help/projects-v2/insights-x-axis.png) +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. + ![Screenshot showing selecting a grouping method](/assets/images/help/projects-v2/insights-group.png) +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. + ![Screenshot showing selecting what to display on the y axis](/assets/images/help/projects-v2/insights-y-axis.png) +1. To save your chart, click **Save changes**. + ![Screenshot showing the save button](/assets/images/help/projects-v2/insights-save.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md new file mode 100644 index 0000000000..e07534f9f2 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md @@ -0,0 +1,20 @@ +--- +title: 'Creating charts' +intro: 'Learn how to create new charts to save your configurations.' +miniTocMaxHeadingLevel: 3 +versions: + feature: "projects-v2" +type: tutorial +product: '{% data reusables.gated-features.historical-insights-for-projects %}' +topics: + - Projects +--- + +{% data reusables.projects.access-insights %} +3. In the menu on the left, click **New chart**. + ![Screenshot showing the new chart button](/assets/images/help/projects-v2/insights-new-chart.png) +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 Return. + ![Screenshot showing how to rename a chart](/assets/images/help/projects-v2/insights-rename.png) +5. Above the chart, type filters to change the data used to build the chart. For more information, see "[Filtering projects](/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**. + ![Screenshot showing save button](/assets/images/help/projects-v2/insights-save-filter.png) \ No newline at end of file diff --git a/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md new file mode 100644 index 0000000000..3502718aa5 --- /dev/null +++ b/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md @@ -0,0 +1,16 @@ +--- +title: 'Viewing insights from your {% data variables.projects.project_v2 %}' +shortTitle: 'Viewing insights' +intro: '...' +versions: + feature: "projects-v2" +topics: + - Issues + - Projects +product: '{% data reusables.gated-features.historical-insights-for-projects %}' +children: + - /about-insights-for-projects + - /creating-charts + - /configuring-charts +allowTitleToDifferFromFilename: true +--- diff --git a/content/issues/tracking-your-work-with-issues/about-issues.md b/content/issues/tracking-your-work-with-issues/about-issues.md index c54499f21a..7464e07f11 100644 --- a/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/content/issues/tracking-your-work-with-issues/about-issues.md @@ -31,7 +31,7 @@ Issues can be created in a variety of ways, so you can choose the most convenien You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones. -For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)." +For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." {% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)." ## Stay up to date diff --git a/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md index a25ffa5e3e..c436e96ae1 100644 --- a/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -89,24 +89,32 @@ Once you have created a label in a repository, you can apply it on any issue, pu Below is an example of a `front-end` label that we created and added to the issue. ![Adding a label to an issue example](/assets/images/help/issues/quickstart-add-label-to-issue.png) + ## Adding issues to a project board -{% ifversion fpt or ghec %}You can use projects on {% data variables.product.prodname_dotcom %}, currently in limited public beta, to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects (beta)](/issues/trying-out-the-new-projects-experience/quickstart)." -### Project (beta) example + +{% ifversion projects-v2 %} + +You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." +### Project example Here is the table layout of an example project, populated with the Project Octocat issues we have created. -![Projects (beta) table layout example](/assets/images/help/issues/quickstart-projects-table-view.png) +![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png) We can also view the same project as a board. -![Projects (beta) board layout example](/assets/images/help/issues/quickstart-projects-board-view.png) +![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png) {% endif %} +{% ifversion projects-v1 %} -You can {% ifversion fpt or ghec %} also use the existing{% else %} use{% endif %} project boards on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." ### Project board example Below is a project board for our example Project Octocat with the issue we created, and the smaller issues we broke it down into, added to it. ![Project board example](/assets/images/help/issues/quickstart-project-board.png) + +{% endif %} + ## Next steps You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work. @@ -116,6 +124,6 @@ You have now learned about the tools {% data variables.product.prodname_dotcom % - "[About issues and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" for learning more about issue templates - "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" for learning how to create, edit and delete labels - "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" for learning more about task lists -{% ifversion fpt or ghec %} - "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" for learning more about the new projects experience, currently in limited public beta -- "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)" for learning how to customize views for projects, currently in limited public beta{% endif %} -- "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards +{% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects +- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %} +{% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %} diff --git a/content/issues/tracking-your-work-with-issues/quickstart.md b/content/issues/tracking-your-work-with-issues/quickstart.md index 06fb0055f4..eebf0af0c7 100644 --- a/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/content/issues/tracking-your-work-with-issues/quickstart.md @@ -71,7 +71,7 @@ To communicate responsibility, you can assign the issue to a member of your orga ## Adding the issue to a project -You can add the issue to an existing project. {% ifversion fpt or ghec %}If you are using projects (beta), you can also populate metadata for the project. {% endif %} For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)". +You can add the issue to an existing project{% ifversion projects-v2 %} and populate metadata for the project. {% endif %} For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} ![issue with projects](/assets/images/help/issues/issue-project.png) @@ -97,5 +97,5 @@ You can use issues for a wide range of purposes. For example: Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}: - To learn more about issues, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)." -- To learn more about how projects can help you with planning and tracking, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" or {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)". +- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} - To learn more about using issue templates{% ifversion fpt or ghec %} and issue forms{% endif %} to encourage contributors to provide specific information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." diff --git a/content/issues/trying-out-the-new-projects-experience/about-projects.md b/content/issues/trying-out-the-new-projects-experience/about-projects.md deleted file mode 100644 index 92154685b4..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/about-projects.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: About projects (beta) -intro: 'Projects are a customizable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.' -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' - ghec: '*' -type: overview -topics: - - Projects ---- - -{% data reusables.projects.projects-beta %} - -## About projects - -A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. You can also add custom fields to track metadata. Projects are flexible so that your team can work in the way that is best for them. - -### Staying up-to-date - -Your project automatically stays up-to-date with the information on {% data variables.product.company_short %}. When a pull request or issue changes, your project reflects that change. This integration also works both ways, so that when you change information about a pull request or issue from your project, the pull request or issue reflects that information. - -### Adding metadata to your tasks - -You can use custom fields to add metadata to your tasks. For example, you can track the following metadata: - -- a date field to track target ship dates -- a number field to track the complexity of a task -- a single select field to track whether a task is Low, Medium, or High priority -- a text field to add a quick note -- an iteration field to plan work week-by-week, including support for breaks - -### Viewing your project from different perspectives - -You can view your project as a high density table layout: - -![Project table](/assets/images/help/issues/projects_table.png) - -Or as a board: - -![Project board](/assets/images/help/issues/projects_board.png) - -To help you focus on specific aspects of your project, you can group, sort, or filter items: - -![Project view](/assets/images/help/issues/project_view.png) - -For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." - -### Working with the project command palette - -You can use the project command palette to quickly change views or add fields. The command palette guides you so that you don't need to memorize custom keyboard shortcuts. For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." - -### Automating project management tasks - -Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." - -## Comparing projects (beta) with the non-beta projects - -Projects (beta) is a new, customizable version of projects. For more information about the non-beta version of projects, see "[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." - -## Sharing feedback - -You can share your feedback about projects (beta) with {% data variables.product.company_short %}. To join the conversation, see [the feedback discussion](https://github.com/github/feedback/discussions/categories/issues-feedback). diff --git a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/content/issues/trying-out-the-new-projects-experience/creating-a-project.md deleted file mode 100644 index f4721a25bc..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -title: Creating a project (beta) -intro: 'Learn how to make a project, populate it, and add custom fields.' -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' - ghec: '*' -type: tutorial -topics: - - Projects ---- - -Projects are a customizable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you jot down. You can add custom fields and create views for specific purposes. - -{% data reusables.projects.projects-beta %} - -## Creating a project - -### Creating an organization project - -{% data reusables.projects.create-project %} - -### Creating a user project - -{% data reusables.projects.create-user-project %} - -## Updating your project description and README - -{% data reusables.projects.project-description %} - -## Adding items to your project - -Your project can track draft issues, issues, and pull requests. - -### Creating draft issues - -Draft issues are useful to quickly capture ideas. - -1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. -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**. - -Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](#converting-draft-issues-to-issues)." - -{% note %} - -**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue. - -{% endnote %} - -### Issues and pull requests - -#### Paste the URL of an issue or pull request - -1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. -1. Paste the URL of the issue or pull request. - -#### Searching for an issue or pull request - -1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. -2. Enter #. -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. - -#### Adding multiple issues or pull requests from a repository - -1. On {% data variables.product.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project. -{% data reusables.repositories.sidebar-issue-pr %} -1. To the left of each issue title, select the issues that you want to add to your project. - ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png) -1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. - ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png) -1. Above the list of issues or pull requests, click **Projects (beta)**. - ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/projects-beta-assign-button.png) -1. Click the projects you want to add the selected issues or pull requests to. - ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/projects-beta-assign-dropdown.png) - -#### Assigning a project from within an issue or pull request - -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. - - ![Project sidebar](/assets/images/help/issues/project_side_bar.png) - -## Converting draft issues to issues - -In table layout: - -1. Click the {% octicon "triangle-down" 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. -4. Alternatively, edit the `labels`, `milestone`, or `repository` fields of the draft issue that you want to convert. - -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. - -## Removing items from your project - -You can archive an item to keep the context about the item in the project but remove it from the project views. You can delete an item to remove it from the project entirely. - -1. Select the item(s) to archive or delete. To select multiple items, do one of the following: - - Command+Click (Mac) or Ctrl+Click (Windows/Linux) each item. - - Select an item then Shift+↑ or Shift+↓ to select additional items above or below the initially selected item. - - Select an item then Shift+Click another item to select all items between the two items. - - Enter Command+A (Mac) or Ctrl+A (Windows/Linux) to select all items in a column in a board layout or all items in a table layout. -2. To archive all selected items, enter E. To delete all selected items, enter Del. Alternatively, select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout), then select the desired action. - -You can restore archived items but not deleted items. For more information, see [Restoring archived items](#restoring-archived-items). - -## Restoring archived items - -1. Navigate to your project. -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. -1. In the menu, click **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 "[Filtering projects (beta)](/issues/trying-out-the-new-projects-experience/filtering-projects)." - - ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png) - -1. To the left of each item title, select the items you would like to restore. - - ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png) - -1. To restore the selected items, above the list of items, click **Restore**. - - ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png) - -## Adding fields - -As field values change, they are automatically synced so that your project and the items that it tracks are up-to-date. - -### Showing existing fields - -Your project tracks up-to-date information about issues and pull requests, including any changes to the title, assignees, labels, milestones, repository, reviewers, and linked pull requests. When your project initializes, "title" and "assignees" are displayed; the other fields are hidden. You can change the visibility of these fields in your project. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "show". -3. Select the desired command (for example: "Show: Repository"). - -Alternatively, you can do this in the UI: - -1. Click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. - ![Show or hide fields](/assets/images/help/issues/projects_fields_menu.png) -2. Select the field(s) that you want to display or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed. - -### Adding custom fields - -You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project. - -Custom fields can be text, number, date, single select, or iteration: - -- Text: The value can be any text. -- Number: The value must be a number. -- Date: The value must be a date. -- Single select: The value must be selected from a set of specified values. -- Iteration: The value must be selected from a set of date ranges (iterations). Iterations in the past are automatically marked as "completed", and the iteration covering the current date range is marked as "current". For more information, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)." - -1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it. -2. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**. -3. A popup will appear for you to enter information about the new field. - ![New field](/assets/images/help/issues/projects_new_field.png) -4. In the text box, enter a name for the new field. -5. Select the dropdown menu and click the desired type. -6. If you specified **Single select** as the type, enter the options. -7. If you specified **Iteration** as the type, enter the start date of the first iteration and the duration of the iteration. Three iterations are automatically created, and you can add additional iterations on the project's settings page. - -You can also edit your custom fields. - -{% data reusables.projects.project-settings %} -1. Under **Fields**, select the field that you want to edit. -1. For single select fields, you can add, delete, or reorder the options. -1. For iteration fields, you can add or delete iterations, change iteration names, and change the start date and duration of the iteration. - - For more information on modifying iteration fields, see "[Managing iterations in projects](/issues/trying-out-the-new-projects-experience/managing-iterations)." - -## Customizing your views - -You can view your project as a table or board, group items by field, filter item, and more. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." - -## Configuring built-in automation - -{% data reusables.projects.about-workflows %} - -You can enable or disable the built-in workflows for your project. - -{% data reusables.projects.enable-basic-workflow %} - -## Adding your project to a repository - -You can list relevant projects in a repository. You can only list projects that are owned by the same user or organization that owns the repository. - -In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[Managing the visibility of your projects (beta)](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)" and "[Managing access to projects (beta)](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)." - -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 **Projects (Beta)** in the side bar. -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. diff --git a/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md deleted file mode 100644 index 0b689f06e5..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -title: Customizing your project (beta) views -intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.' -allowTitleToDifferFromFilename: true -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Projects ---- - -{% data reusables.projects.projects-beta %} - -## Project command palette - -Use the project command palette to quickly change settings and run commands in your project. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands. - -## Changing the project layout - -You can view your project as a table or as a board. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Switch layout". -3. Choose the required command. For example, **Switch layout: Table**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Table** or **Board**. - -## Showing and hiding fields - -You can show or hide a specific field. - -### Showing and hiding fields in table layout - -1. {% data reusables.projects.open-command-palette %} -2. Start typing the action you want to take ("show" or "hide") or the name of the field. -3. Choose the required command. For example, **Show: Milestone**. - -Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name and click **Hide field**. - -### Showing and hiding fields in board layout - -1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name. -2. Under **configuration**, click {% octicon "list-unordered" aria-label="the unordered list icon" %}. -3. In the menu that's displayed, select fields to add them and deselect fields to remove them from the view. - -## Reordering fields - -You can change the order of fields. - -1. Click the field header. -2. While clicking, drag the field to the required location. - -## Reordering rows - -In table layout, you can change the order of rows. - -1. Click the number at the start of the row. -2. While clicking, drag the row to the required location. - -## Sorting by field values - -In table layout, you can sort items by a field value. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Sort by" or the name of the field you want to sort by. -3. Choose the required command. For example, **Sort by: Assignees, asc**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**. - -{% note %} - -**Note:** When a table is sorted, you cannot manually reorder rows. - -{% endnote %} - -Follow similar steps to remove a sort. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Remove sort-by". -3. Choose **Remove sort-by**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name and click the menu item that indicates the current sort. - -## Grouping by field values in table layout - -In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group. - -{% note %} - -**Note:** Currently, you cannot group by title, labels, reviewers, or linked pull requests. - -{% endnote %} - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Group by" or the name of the field you want to group by. -3. Choose the required command. For example, **Group by: Status**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the field name that you want to group by and click **Group by values**. - -Follow similar steps to remove a grouping. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Remove group-by". -3. Choose **Remove group-by**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the view name and click the menu item that indicates the current grouping. - -## Setting the column field in board layout - -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`. - -1. {% data reusables.projects.open-command-palette %} -1. Start typing "Column field by" or the name of the field you want to use for your columns. -1. Choose the required command. For example, **Column field by: Status**. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the board view that you want to modify and click {% octicon "columns" aria-label="the column icon" %} **Column field**. Then select the field that you want to use for the board columns. - -## Filtering items - -Click {% octicon "filter" aria-label="the filter icon" %} at the top of the table to show the "Filter by keyword or by field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear. - -{% data reusables.projects.projects-filters %} - -Alternatively, use the command palette. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Filter by" or the name of the field you want to filter by. -3. Choose the required command. For example, **Filter by Status**. -4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status"). - -In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again. - -For more information, see "[Filtering projects](/issues/trying-out-the-new-projects-experience/filtering-projects)." - -## Creating a project view - -Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. - -For example, you can have: -- A view that shows all items not yet started (filter on "Status"). -- A view that shows the workload for each team (group by a custom "Team" field). -- A view that shows the items with the earliest target ship date (sort by a date field). - -To add a new view: - -1. {% data reusables.projects.open-command-palette %} -2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view). -3. Choose the required command. - -Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Duplicate view**. - -The new view is automatically saved. - -## Saving changes to a view - -When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. - -![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png) - -If you don't want to save the changes, you can ignore this indicator. No one else will see your changes. - -To save the current configuration of the view for all project members: -1. {% data reusables.projects.open-command-palette %} -1. Start typing "Save view" or "Save changes to new view". -1. Choose the required command. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Save view** or **Save changes to new view**. - -## Reordering saved views - -To change the order of the tabs that contain your saved views, click and drag a tab to a new location. - -The new tab order is automatically saved. - -## Renaming a saved view - -To rename a view: -1. Double click the name in the project tab. -1. Change the name. -1. Press Enter, or click outside of the tab. - -The name change is automatically saved. - -## Deleting a saved view - -To delete a view: -1. {% data reusables.projects.open-command-palette %} -2. Start typing "Delete view". -3. Choose the required command. - -Alternatively, click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to a view name and click **Delete view**. - -## Further reading - -- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" -- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)" diff --git a/content/issues/trying-out-the-new-projects-experience/filtering-projects.md b/content/issues/trying-out-the-new-projects-experience/filtering-projects.md deleted file mode 100644 index db4cdecb95..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/filtering-projects.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Filtering projects (beta) -intro: You can filter your projects to focus on specific information. -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 -versions: - fpt: '*' - ghec: '*' -topics: - - Projects - - Organizations ---- - -{% data reusables.projects.projects-beta %} - -## About filtering projects - -You can customize 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 "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." - -To filter a project, 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 command pallet and type "Filter by" to choose from the available filters. - -The same filters are available for insights, allowing you to filter the data used to create your charts. For more information, see "[Using insights with projects](/issues/trying-out-the-new-projects-experience/using-insights-with-projects)." - -## Syntax for filtering projects - -{% data reusables.projects.projects-filters %} diff --git a/content/issues/trying-out-the-new-projects-experience/index.md b/content/issues/trying-out-the-new-projects-experience/index.md deleted file mode 100644 index 9c5acfe3b4..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Trying out the new projects experience -shortTitle: Projects (beta) -intro: 'Build customized projects to track your work in {% data variables.product.company_short %}.' -versions: - fpt: '*' - ghec: '*' -topics: - - Issues - - Projects -children: - - /about-projects - - /quickstart - - /creating-a-project - - /migrating-your-project - - /managing-iterations - - /customizing-your-project-views - - /filtering-projects - - /using-the-api-to-manage-projects - - /automating-projects - - /managing-projects - - /managing-the-visibility-of-your-projects - - /managing-access-to-projects - - /using-insights-with-projects - - /best-practices-for-managing-projects ---- - diff --git a/content/issues/trying-out-the-new-projects-experience/managing-iterations.md b/content/issues/trying-out-the-new-projects-experience/managing-iterations.md deleted file mode 100644 index 9a4da9455a..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/managing-iterations.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Managing iterations in projects (beta) -intro: You can create iterations to plan upcoming work and group items. -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 -versions: - fpt: '*' - ghec: '*' -topics: - - Projects - - Organizations ---- - -{% data reusables.projects.projects-beta %} - -## About iterations - -You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to focus on a single iteration, and sort by iteration. - -When you first create an iteration field, three iterations are automatically created. You can add additional iterations and make other changes on your project's settings page. - -![Screenshot showing the settings for an iteration field](/assets/images/help/issues/iterations-example.png) - -## Creating an iteration field - -You can create an iteration field using the command palette or the project's interface. - -1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it. - - Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**. -1. In the text box, enter a name for the new iteration field. -1. Select the dropdown menu below and click **Iteration**. -1. Optionally, if you want to change the starting date from the current day, select the calendar dropdown next to "Starts on" and click on a new starting date. -2. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**. -3. Click **Save & create**. - -## Adding new iterations - -{% 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" %} next to "Add iteration", 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**. - -{% data reusables.projects.project-settings %} -1. 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. Click **Save changes**. - -## Inserting a break - -You can insert breaks into your iterations to communicate when you are taking time away from scheduled work. The duration of a new break defaults to the length of the most recently created iteration. - -{% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. -2. On the dividing line above an iteration and to the right, click **Insert break**. - ![Screenshot showing location of "Insert break" button](/assets/images/help/issues/iteration-insert-break.png) -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**. diff --git a/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md b/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md deleted file mode 100644 index 147f39eb56..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Managing the visibility of your projects (beta) -intro: You can control who can view your projects. -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' - ghec: '*' -topics: - - Projects - - Organizations ---- - -{% data reusables.projects.projects-beta %} - -## About project visibility - -Projects (beta) can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project. - -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 with hidden item](/assets/images/help/projects/hidden-items.png) - -Only project admins can control project visibility. - -In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI. - -Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to projects](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)." - -## Changing project visibility - -{% data reusables.projects.project-settings %} -1. Under **Visibility**, select **Private** or **Public**. diff --git a/content/issues/trying-out-the-new-projects-experience/quickstart.md b/content/issues/trying-out-the-new-projects-experience/quickstart.md deleted file mode 100644 index 3b08dca27d..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/quickstart.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -title: Quickstart for projects (beta) -intro: 'Experience the speed, flexibility, and customization of projects (beta) by creating a project in this interactive guide.' -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' - ghec: '*' -type: quick_start -topics: - - Projects ---- - -{% data reusables.projects.projects-beta %} - -## Introduction - -This guide demonstrates how to use projects (beta) to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators. - -## Prerequisites - -You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." - -In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)." - -## Creating a project - -First, create an organization project or a user project. - -### Creating an organization project - -{% data reusables.projects.create-project %} - -### Creating a user project - -{% data reusables.projects.create-user-project %} - -## Setting your project description and README - -{% data reusables.projects.project-description %} - -## Adding issues to your project - -Next, add a few issues to your project. - -When your new project initializes, it prompts you to add items to your project. If you lose this view or want to add more issues later, place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. - -1. Type `#`. -2. Select the repository where your issue is located. To narrow down the options, you can start typing a part of the repository name. -3. Select your issue. To narrow down the options, you can start typing a part of the issue title. - -Repeat the above steps a few times to add multiple issues to your project. - -For more information about other ways to add issues to your project, or about other items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)." - -## Adding draft issues to your project - -Next, add a draft issue to your project. - -1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. -1. Type your idea, then press **Enter**. -1. Click on the title of the draft issue. In the markdown input box that appears, enter the some more information about your idea, then click **Save**. - -## Creating a field to track priority - -Now, create a custom field called `Priority` to contain the values: `High`, `Medium`, or `Low`. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing any part of "Create new field". -3. Select **Create new field**. -4. In the resulting pop-up, enter `Priority` in the text box. -5. In the drop-down, select **Single select**. -6. Add options for `High`, `Medium`, and `Low`. You can also include emojis in your options. - ![New single select field example](/assets/images/help/projects/new-single-select-field.png) -7. Click **Save**. - -Specify a priority for all issues in your project. - -![Example priorities](/assets/images/help/projects/priority_example.png) - -## Grouping issues by priority - -Next, group all of the items in your project by priority to make it easier to focus on the high priority items. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing any part of "Group by". -3. Select **Group by: Priority**. - -Now, move issues between groups to change their priority. - -1. Choose an issue. -2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group. - -![Move issue between groups](/assets/images/help/projects/move_between_group.gif) - -## Saving the priority view - -When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority. - -1. Select the drop-down menu next to the view name. -2. Click **Save changes**. - -To indicate the purpose of the view, give it a descriptive name. - -1. Place your cursor in the current view name, **View 1**. -2. Replace the existing text with the new name, `Priorities`. - -You can share the URL with your team to keep everyone aligned on the project priorities. - -When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified. - -## Adding a board layout - -To view the progress of your project's issues, you can switch to board layout. - -The board layout is based on the status field, so specify a status for each issue in your project. - -![Example status](/assets/images/help/projects/status_example.png) - -Then, create a new view. - -1. Click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view. - -Next, switch to board layout. - -1. {% data reusables.projects.open-command-palette %} -2. Start typing any part of "Switch layout: Board". -3. Select **Switch layout: Board**. - ![Example priorities](/assets/images/help/projects/example_board.png) - -When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future. - -1. Select the drop-down menu next to the view name. -2. Click **Save changes**. - -To indicate the purpose of the view, give it a descriptive name. - -1. Place your cursor in the current view name, **View 2**. -2. Replace the existing text with the new name, `Progress`. - -![Example priorities](/assets/images/help/projects/project-view-switch.gif) - -## Configure built-in automation - -Finally, add a built in workflow to set the status to **Todo** when an item is added to your project. - -1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}. -2. Under **Default workflows**, click **Item added to project**. -3. Next to **When**, ensure that both `issues` and `pull requests` are selected. -4. Next to **Set**, select **Status:Todo**. -5. Click the **Disabled** toggle to enable the workflow. - -## Next steps - -You can use projects for a wide range of purposes. For example: - -- Track work for a release -- Plan a sprint -- Prioritize a backlog - -Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}: - -- To provide feedback about the projects (beta) experience, go to the [GitHub feedback repository](https://github.com/github/feedback/discussions/categories/issues-feedback). -- To learn more about how projects can help you with planning and tracking, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)." -- To learn more about the fields and items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." -- To learn about more ways to display the information you need, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)." diff --git a/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md b/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md deleted file mode 100644 index c885ea9641..0000000000 --- a/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Using insights with projects (beta) -intro: You can view and customize charts that are built from your project's data. -allowTitleToDifferFromFilename: true -miniTocMaxHeadingLevel: 2 -versions: - fpt: '*' - ghec: '*' -topics: - - Projects - - Organizations ---- - -{% data reusables.projects.insights-alpha %} - -## About insights - -You can use insights to view and customize charts that use the items added to your project as their source data. The default "Burn up" chart shows item status over time, allowing you to visualize progress and spot patterns over time. - -![Screenshot showing an example of the default burn up chart for the current iteration](/assets/images/help/issues/burnup-example.png) - -You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, and the information displayed, and the chart is available to anyone that can view the project. - -![Screenshot showing an stacked column chart showing item types for each iteration](/assets/images/help/issues/column-chart-example.png) - -## Creating a chart - -{% 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 Return. -5. Above the chart, type filters to change the data used to build the chart. For more information, see "[Filtering projects](/issues/trying-out-the-new-projects-experience/filtering-projects)." -6. To the right of the filter text box, click **Save changes**. - -## Configuring a chart - -{% 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**. diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md index 32d4aa5a3f..d2ca75bb1b 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Adding an outside collaborator to a project board in your organization -intro: 'As an organization owner or project board admin, you can add an outside collaborator and customize their permissions to a project board.' +title: Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.' redirect_from: - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization @@ -13,13 +13,17 @@ topics: - Organizations - Teams shortTitle: Add a collaborator +allowTitleToDifferFromFilename: true --- -An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your organization. +{% data reusables.projects.project_boards_old %} + +An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization. {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/content/organizations/managing-access-to-your-organizations-project-boards/index.md index 9606c54fbb..0ea88937f3 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/index.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -1,6 +1,6 @@ --- -title: Managing access to your organization’s project boards -intro: 'As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.' +title: Managing access to your organization’s {% data variables.product.prodname_projects_v1 %} +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.' redirect_from: - /articles/managing-access-to-your-organization-s-project-boards - /articles/managing-access-to-your-organizations-project-boards @@ -20,6 +20,7 @@ children: - /managing-an-individuals-access-to-an-organization-project-board - /adding-an-outside-collaborator-to-a-project-board-in-your-organization - /removing-an-outside-collaborator-from-an-organization-project-board -shortTitle: Manage project board access +shortTitle: Manage {% data variables.product.prodname_project_v1 %} access +allowTitleToDifferFromFilename: true --- diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md index be34c8beea..d665469a0f 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -1,6 +1,6 @@ --- -title: Managing access to a project board for organization members -intro: 'As an organization owner or project board admin, you can set a default permission level for a project board for all organization members.' +title: Managing access to a {% data variables.product.prodname_project_v1 %} for organization members +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.' redirect_from: - /articles/managing-access-to-a-project-board-for-organization-members - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members @@ -13,21 +13,25 @@ topics: - Organizations - Teams shortTitle: Manage access for members +allowTitleToDifferFromFilename: true --- -By default, organization members have write access to their organization's project boards unless organization owners or project board admins set different permissions for specific project boards. +{% data reusables.projects.project_boards_old %} + +By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}. ## Setting a baseline permission level for all organization members {% tip %} -**Tip:** You can give an organization member higher permissions to project board. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} @@ -37,6 +41,6 @@ By default, organization members have write access to their organization's proje ## Further reading -- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md index ebafc21d9f..7d5d783f39 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: Managing an individual’s access to an organization project board -intro: 'As an organization owner or project board admin, you can manage an individual member''s access to a project board owned by your organization.' +title: Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %} +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.' redirect_from: - /articles/managing-an-individual-s-access-to-an-organization-project-board - /articles/managing-an-individuals-access-to-an-organization-project-board @@ -14,19 +14,23 @@ topics: - Organizations - Teams shortTitle: Manage individual access +allowTitleToDifferFromFilename: true --- +{% data reusables.projects.project_boards_old %} + {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endnote %} -## Giving an organization member access to a project board +## Giving an organization member access to a {% data variables.projects.projects_v1_board %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} @@ -36,24 +40,26 @@ shortTitle: Manage individual access {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} -## Changing an organization member's access to a project board +## Changing an organization member's access to a {% data variables.projects.projects_v1_board %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %} -## Removing an organization member's access to a project board +## Removing an organization member's access to a {% data variables.projects.projects_v1_board %} -When you remove a collaborator from a project board, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a project board, you must remove access for each role the person has. For instance, a person may have access to the project board as an organization member or team member. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} @@ -62,4 +68,4 @@ When you remove a collaborator from a project board, they may still retain acces ## Further reading -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index e495605761..7aa452326b 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: Managing team access to an organization project board -intro: 'As an organization owner or project board admin, you can give a team access to a project board owned by your organization.' +title: Managing team access to an organization {% data variables.product.prodname_project_v1 %} +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.' redirect_from: - /articles/managing-team-access-to-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board @@ -13,29 +13,33 @@ topics: - Organizations - Teams shortTitle: Manage team access +allowTitleToDifferFromFilename: true --- +{% data reusables.projects.project_boards_old %} + {% warning %} **Warnings:** -- You can change a team's permission level if the team has direct access to a project board. If the team's access to the project board is inherited from a parent team, you must change the parent team's access to the project board. -- If you add or remove project board access for a parent team, each of that parent's child teams will also receive or lose access to the project board. For more information, see "[About teams](/articles/about-teams)." +- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}. +- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. For more information, see "[About teams](/articles/about-teams)." {% endwarning %} -## Giving a team access to a project board +## Giving a team access to a {% data variables.projects.projects_v1_board %} -You can give an entire team the same permission level to a project board. +You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}. {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a project board, and a project board admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the project board. For more information see, "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endnote %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} @@ -45,14 +49,14 @@ You can give an entire team the same permission level to a project board. 10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**. ![Team permissions drop-down menu with read, write, and admin options](/assets/images/help/projects/org-project-team-choose-permissions.png) -## Configuring a team's access to a project board +## Configuring a team's access to a {% data variables.projects.projects_v1_board %} -If a team's access to a project board is inherited from a parent team, you must change the parent team's access to the project board to update access to the child teams. +If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams. {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} 4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png) -5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trash" aria-label="The trash icon" %}**. +5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png) diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md index 2123ca4ac1..cdb23eca2e 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -1,6 +1,6 @@ --- -title: Project board permissions for an organization -intro: 'Organization owners and people with project board admin permissions can customize who has read, write, and admin permissions to your organization’s project boards.' +title: '{% data variables.product.prodname_project_v1_caps %} permissions for an organization' +intro: 'Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize who has read, write, and admin permissions to your organization’s {% data variables.projects.projects_v1_boards %}.' redirect_from: - /articles/project-board-permissions-for-an-organization - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization @@ -12,35 +12,38 @@ versions: topics: - Organizations - Teams -shortTitle: Project board permissions +shortTitle: '{% data variables.product.prodname_project_v1_caps %} permissions' +allowTitleToDifferFromFilename: true --- +{% data reusables.projects.project_boards_old %} + ## Permissions overview -There are three levels of permissions to a project board for people and teams: +There are three levels of permissions to a {% data variables.projects.projects_v1_board %} for people and teams: {% data reusables.project-management.project-board-permissions %} -Organization owners and people with admin permissions can give a person access to an organization project board individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization. +Organization owners and people with admin permissions can give a person access to an organization {% data variables.projects.projects_v1_board %} individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization. -Organization owners and people with admin permissions to a project board can also: +Organization owners and people with admin permissions to a {% data variables.projects.projects_v1_board %} can also: - Set default project board permissions for all organization members. -- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." -- Manage project board visibility. For more information, see "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." +- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." +- Manage project board visibility. For more information, see "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." -## Cascading permissions for project boards +## Cascading permissions for {% data variables.projects.projects_v1_boards %} {% data reusables.project-management.cascading-permissions %} -For example, if an organization owner has given all organization members read permissions to a project board, and a project board admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the project board. +For example, if an organization owner has given all organization members read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the {% data variables.projects.projects_v1_board %}. -## Project board visibility +## {% data variables.projects.projects_v1_board_caps %} visibility -{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)." +{% data reusables.project-management.project-board-visibility %} You can change the {% data variables.projects.projects_v1_board %}'s visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)." ## Further reading -- "[Changing project board visibility](/articles/changing-project-board-visibility)" -- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" -- "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)" +- "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility)" +- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)" +- "[Managing access to a {% data variables.product.prodname_project_v1 %} for organization members](/articles/managing-access-to-a-project-board-for-organization-members)" diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md index b0f09b56ed..1ced0b0208 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: Removing an outside collaborator from an organization project board -intro: 'As an organization owner or project board admin, you can remove an outside collaborator''s access to a project board.' +title: Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %} +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.' redirect_from: - /articles/removing-an-outside-collaborator-from-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board @@ -13,11 +13,15 @@ topics: - Organizations - Teams shortTitle: Remove outside collaborator +allowTitleToDifferFromFilename: true --- +{% data reusables.projects.project_boards_old %} + {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -{% data reusables.organizations.organization-wide-project %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} diff --git a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..0db3747d40 --- /dev/null +++ b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: 'Allowing project visibility changes in your organization' +intro: 'Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization.' +versions: + feature: "projects-v2" +topics: + - Organizations + - Projects +shortTitle: 'Project visibility permissions' +allowTitleToDifferFromFilename: true +permissions: Organization owners can allow project visibility changes for an organization. +--- + +You can restrict who has the ability to change the visibility of projects in your organization, such as restricting members from changing a project from private to public. + +You can limit the ability to change project visibility to just organization owners, or you can allow anyone with admin permissions on a project to change the visibility. + +{% data reusables.profile.access_org %} +{% 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**. + ![Screenshot showing checkbox to set visibility changes](/assets/images/help/projects-v2/visibility-change-checkbox.png) +1. Click **Save**. + +## Further reading + +- "[Managing visibility of your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" \ No newline at end of file diff --git a/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md new file mode 100644 index 0000000000..f67fa5df99 --- /dev/null +++ b/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: 'Disabling insights for {% data variables.projects.projects_v2 %} in your organization' +intro: Organization owners can turn off insights for {% data variables.product.prodname_projects_v2 %} in their organization. +versions: + feature: "projects-v2" +product: '{% data reusables.gated-features.historical-insights-for-projects %}' +topics: + - Projects +shortTitle: Disable {% data variables.product.prodname_projects_v2 %} insights +allowTitleToDifferFromFilename: true +--- + +After you disable insights for projects in your organization, it won't be possible to access insights for any projects owned by the organization. + + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**. + ![Screenshot showing features menu item](/assets/images/help/projects-v2/features-org-menu.png) +1. Under "Insights", deselect **Enable Insights for the organization**. + ![Screenshot showing Enable Insights for the organization checkbox](/assets/images/help/projects-v2/disable-insights-checkbox.png) +1. Click **Save**. + ![Screenshot showing save button](/assets/images/help/projects-v2/disable-insights-save.png) + +## Further reading + +- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" +- "[About insights for {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)" diff --git a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md index c83355b58f..01bd82747c 100644 --- a/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md +++ b/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Disabling project boards in your organization -intro: Organization owners can turn off organization-wide project boards and repository project boards in an organization. +title: 'Disabling {% ifversion projects-v2 %}projects{% else %}project boards{% endif %} in your organization' +intro: 'Organization owners can turn off {% ifversion projects-v2 %}organization-wide {% data variables.projects.projects_v2 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %}{% else %}organization-wide project boards and repository project boards{% endif %} in an organization.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization - /articles/disabling-project-boards-in-your-organization @@ -12,12 +12,14 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Disable project boards +shortTitle: Disable projects +allowTitleToDifferFromFilename: true --- -After you disable organization-wide project boards, it won’t be possible to create new project boards at the organization level, and any existing organization-level project boards will become inaccessible at their previous URLs. Project boards in repositories in the organization are not affected. +After you disable organization-wide project boards, it won’t be possible to create new project boards at the organization level, and any existing organization-level project boards will become inaccessible at their previous URLs. Project boards in repositories in the organization are not affected. {% ifversion projects-v2 %}These settings apply to {% data variables.projects.projects_v2 %} and {% data variables.projects.projects_v1_boards %}.{% endif %} After you disable repository project boards in an organization, it won't be possible to create new project boards in any repositories in the organization, and any existing project boards in repositories in the organization will become inaccessible at their previous URLs. Project boards at the organization level are not affected. + When you disable project boards, you will no longer see project board information in timelines or [audit logs](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). @@ -36,7 +38,8 @@ When you disable project boards, you will no longer see project board informatio ## Further reading -- "[About project boards](/articles/about-project-boards)" -- "[Closing a project board](/articles/closing-a-project-board)" -- "[Deleting a project board](/articles/deleting-a-project-board)" -- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)" +{% ifversion projects-v2 %}- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"{% endif %} +- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)" +- "[Closing a {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board)" +- "[Deleting a {% data variables.projects.projects_v1_board %}](/articles/deleting-a-project-board)" +- "[Disabling {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository)" diff --git a/content/organizations/managing-organization-settings/index.md b/content/organizations/managing-organization-settings/index.md index 8a5e001da1..e5818036d4 100644 --- a/content/organizations/managing-organization-settings/index.md +++ b/content/organizations/managing-organization-settings/index.md @@ -41,6 +41,8 @@ children: - /integrating-jira-with-your-organization-project-board - /upgrading-to-the-corporate-terms-of-service - /disabling-project-boards-in-your-organization + - /disabling-insights-for-projects-in-your-organization + - /allowing-project-visibility-changes-in-your-organization shortTitle: Manage organization settings --- {% ifversion fpt or ghec %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md index 8c66c8d326..1f2a9126d6 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md @@ -1,6 +1,6 @@ --- -title: Disabling project boards in a repository -intro: Repository administrators can turn off project boards for a repository if you or your team manages work differently. +title: Disabling {% data variables.projects.projects_v1_boards %} in a repository +intro: Repository administrators can turn off {% data variables.projects.projects_v1_boards %} for a repository if you or your team manages work differently. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository - /articles/disabling-project-boards-in-a-repository @@ -13,13 +13,14 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Disable project boards +shortTitle: Disable {% data variables.projects.projects_v1_boards %} +allowTitleToDifferFromFilename: true --- -When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-your-security-log/). +When you disable {% data variables.projects.projects_v1_boards %}, you will no longer see {% data variables.projects.projects_v1_board %} information in timelines or [audit logs](/articles/reviewing-your-security-log/). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. Under "Features," unselect the **Projects** checkbox. ![Remove Projects checkbox](/assets/images/help/projects/disable-projects-checkbox.png) -After project boards are disabled, existing project boards are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %} +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 %} diff --git a/content/rest/projects/cards.md b/content/rest/projects/cards.md index fb5bef027c..93276cffe8 100644 --- a/content/rest/projects/cards.md +++ b/content/rest/projects/cards.md @@ -1,8 +1,8 @@ --- -title: Project board cards +title: '{% data variables.product.prodname_project_v1_caps %} cards' shortTitle: Cards allowTitleToDifferFromFilename: true -intro: The Project board cards API lets you create and manage cards on a project board. +intro: 'The {% data variables.product.prodname_project_v1 %} cards API lets you create and manage cards on a {% data variables.projects.projects_v1_board %}.' versions: fpt: '*' ghes: '*' diff --git a/content/rest/projects/collaborators.md b/content/rest/projects/collaborators.md index cfb1772eca..381ae8e2db 100644 --- a/content/rest/projects/collaborators.md +++ b/content/rest/projects/collaborators.md @@ -1,8 +1,8 @@ --- -title: Project board collaborators +title: '{% data variables.product.prodname_project_v1_caps %} collaborators' shortTitle: Collaborators allowTitleToDifferFromFilename: true -intro: The Project board collaborators API lets you manage collaborators on a project board. +intro: 'The {% data variables.product.prodname_project_v1 %} collaborators API lets you manage collaborators on a {% data variables.projects.projects_v1_board %}.' versions: fpt: '*' ghes: '*' diff --git a/content/rest/projects/columns.md b/content/rest/projects/columns.md index 9d33009069..2f343bc7f7 100644 --- a/content/rest/projects/columns.md +++ b/content/rest/projects/columns.md @@ -1,8 +1,8 @@ --- -title: Project board columns +title: '{% data variables.product.prodname_project_v1_caps %} columns' shortTitle: Columns allowTitleToDifferFromFilename: true -intro: The Project board columns API lets you create and manage columns on a project board. +intro: 'The {% data variables.product.prodname_project_v1 %} columns API lets you create and manage columns on a {% data variables.projects.projects_v1_board %}.' versions: fpt: '*' ghes: '*' diff --git a/content/rest/projects/index.md b/content/rest/projects/index.md index 629b117bec..7064fbb384 100644 --- a/content/rest/projects/index.md +++ b/content/rest/projects/index.md @@ -1,6 +1,6 @@ --- -title: Projects -intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' +title: '{% data variables.product.prodname_projects_v1_caps %}' +intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create, list, update, delete and customize {% data variables.projects.projects_v1_boards %}.' redirect_from: - /v3/projects - /rest/reference/projects @@ -12,6 +12,7 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 +allowTitleToDifferFromFilename: true children: - /projects - /cards diff --git a/content/rest/projects/projects.md b/content/rest/projects/projects.md index f8af74a412..79c2aaa6b1 100644 --- a/content/rest/projects/projects.md +++ b/content/rest/projects/projects.md @@ -1,8 +1,8 @@ --- -title: Project boards +title: '{% data variables.product.prodname_projects_v1_caps %}' shortTitle: Boards allowTitleToDifferFromFilename: true -intro: The Project boards API lets you create and manage projects in a repository. +intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.' versions: fpt: '*' ghes: '*' diff --git a/data/features/projects-v1.yml b/data/features/projects-v1.yml new file mode 100644 index 0000000000..c217fc003d --- /dev/null +++ b/data/features/projects-v1.yml @@ -0,0 +1,8 @@ +# Issue 6980 +# Projects (classic) +# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning. +versions: + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' diff --git a/data/features/projects-v2.yml b/data/features/projects-v2.yml new file mode 100644 index 0000000000..54ea4f28ad --- /dev/null +++ b/data/features/projects-v2.yml @@ -0,0 +1,6 @@ +# Issue 6980 +# ProjectV2 GA +versions: + fpt: '*' + ghec: '*' + ghae: 'issue-6980' diff --git a/data/reusables/gated-features/historical-insights-for-projects.md b/data/reusables/gated-features/historical-insights-for-projects.md new file mode 100644 index 0000000000..07502e255f --- /dev/null +++ b/data/reusables/gated-features/historical-insights-for-projects.md @@ -0,0 +1 @@ +Historical charts are available with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations. You can save unlimited charts in private projects with {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} for organizations and {% data variables.product.prodname_pro %} for users. Users and organizations using a public project can also save unlimited charts. Users and organizations using {% data variables.product.prodname_free_team %} or a legacy plan can save two charts in private projects. {% data reusables.gated-features.more-info %} \ No newline at end of file diff --git a/data/reusables/project-management/automate-project-board-permissions.md b/data/reusables/project-management/automate-project-board-permissions.md index 525f140e73..b6de4865ba 100644 --- a/data/reusables/project-management/automate-project-board-permissions.md +++ b/data/reusables/project-management/automate-project-board-permissions.md @@ -1 +1 @@ -To set up automatic workflows for a repository project board, you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide project board. +To set up automatic workflows for a repository {% data variables.projects.projects_v1_board %}, you must have write access to the repository. Organization owners and members can configure automatic workflows on an organization-wide {% data variables.projects.projects_v1_board %}. diff --git a/data/reusables/project-management/cascading-permissions.md b/data/reusables/project-management/cascading-permissions.md index 8b84f9e394..d45274e43c 100644 --- a/data/reusables/project-management/cascading-permissions.md +++ b/data/reusables/project-management/cascading-permissions.md @@ -1 +1 @@ -If a person has multiple avenues of access to an organization project board (individually, through a team, or as an organization member), the highest project board permission level overrides lower permission levels. +If a person has multiple avenues of access to an organization {% data variables.projects.projects_v1_board %} (individually, through a team, or as an organization member), the highest {% data variables.projects.projects_v1_board %} permission level overrides lower permission levels. diff --git a/data/reusables/project-management/click-menu.md b/data/reusables/project-management/click-menu.md index 0fd91f018d..e95bfdceb8 100644 --- a/data/reusables/project-management/click-menu.md +++ b/data/reusables/project-management/click-menu.md @@ -1 +1 @@ -1. On the top-right side of the project board, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**. +1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**. diff --git a/data/reusables/project-management/copy-project-boards.md b/data/reusables/project-management/copy-project-boards.md index ce3a80ab6c..118eb3c599 100644 --- a/data/reusables/project-management/copy-project-boards.md +++ b/data/reusables/project-management/copy-project-boards.md @@ -1,3 +1,3 @@ {% ifversion fpt or ghec %} -You can also copy a project board to reuse its customizations for similar projects. For more information, see "[Copying a project board](/articles/copying-a-project-board)." +You can also copy a {% data variables.projects.projects_v1_board %} to reuse its customizations for similar projects. For more information, see "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)." {% endif %} diff --git a/data/reusables/project-management/edit-in-project.md b/data/reusables/project-management/edit-in-project.md index 1c83261282..112ef81842 100644 --- a/data/reusables/project-management/edit-in-project.md +++ b/data/reusables/project-management/edit-in-project.md @@ -1 +1 @@ -You can view and make lightweight edits to issues and pull requests within your project board by clicking on the issue or pull request's title. +You can view and make lightweight edits to issues and pull requests within your {% data variables.projects.projects_v1_board %} by clicking on the issue or pull request's title. diff --git a/data/reusables/project-management/link-repos-to-project-board.md b/data/reusables/project-management/link-repos-to-project-board.md index 0a72db53b6..6bce91fd71 100644 --- a/data/reusables/project-management/link-repos-to-project-board.md +++ b/data/reusables/project-management/link-repos-to-project-board.md @@ -1 +1 @@ -You can link up to twenty-five repositories to your organization or user-owned project board. Linking repositories makes it easier to add issues and pull requests from those repositories to your project board using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar. +You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar. diff --git a/data/reusables/project-management/project-board-permissions.md b/data/reusables/project-management/project-board-permissions.md index 47552a0bd3..cbb4e53a66 100644 --- a/data/reusables/project-management/project-board-permissions.md +++ b/data/reusables/project-management/project-board-permissions.md @@ -1,3 +1,3 @@ -- **Read**, which gives people permission to view a project board. -- **Write**, which gives people permission to view a project board, link repositories to a project board, and interact with a project board. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." -- **Admin**, which gives people permission to view a project board, interact with a project board, manage project board settings, and manage other people's access to the project board. +- **Read**, which gives people permission to view a {% data variables.projects.projects_v1_board %}. +- **Write**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, link repositories to a {% data variables.projects.projects_v1_board %}, and interact with a {% data variables.projects.projects_v1_board %}. For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)." +- **Admin**, which gives people permission to view a {% data variables.projects.projects_v1_board %}, interact with a {% data variables.projects.projects_v1_board %}, manage {% data variables.projects.projects_v1_board %} settings, and manage other people's access to the {% data variables.projects.projects_v1_board %}. diff --git a/data/reusables/project-management/project-board-visibility.md b/data/reusables/project-management/project-board-visibility.md index 7fb24ae2e5..5021c82faf 100644 --- a/data/reusables/project-management/project-board-visibility.md +++ b/data/reusables/project-management/project-board-visibility.md @@ -1 +1 @@ -By default, user-owned and organization-wide project boards are private and only visible to people with read, write, or admin permissions to the project board. {% ifversion ghae %}An internal{% else %}A public{% endif %} project board is visible to {% ifversion ghae %}anyone with access to your enterprise on {% data variables.product.prodname_ghe_managed %}{% elsif ghes %}anyone with access to your {% data variables.product.prodname_ghe_server %} instance{% else %}anyone with the project board's URL{% endif %}. Repository-level project boards share the visibility of their repository. That is, a private repository will have a private board, and this visibility cannot be changed. +By default, user-owned and organization-wide {% data variables.projects.projects_v1_boards %} are private and only visible to people with read, write, or admin permissions to the {% data variables.projects.projects_v1_board %}. {% ifversion ghae %}An internal{% else %}A public{% endif %} {% data variables.projects.projects_v1_board %} is visible to {% ifversion ghae %}any with access to your enterprise{% else %}anyone{% endif %} with the {% data variables.projects.projects_v1_board %}'s URL. Repository-level {% data variables.projects.projects_v1_boards %} share the visibility of their repository. That is, a private repository will have a private project, and this visibility cannot be changed. diff --git a/data/reusables/project-management/project-progress-locations.md b/data/reusables/project-management/project-progress-locations.md index 9ac6c41be9..1df5983464 100644 --- a/data/reusables/project-management/project-progress-locations.md +++ b/data/reusables/project-management/project-progress-locations.md @@ -1 +1 @@ -If progress tracking is enabled, a progress bar appears above the project board, on the project listing page, in the issue sidebar, and in references to the project on other project boards. +If progress tracking is enabled, a progress bar appears above the {% data variables.projects.projects_v1_board %}, on the project listing page, in the issue sidebar, and in references to the project on other {% data variables.projects.projects_v1_boards %}. diff --git a/data/reusables/project-management/resync-automation.md b/data/reusables/project-management/resync-automation.md index 38b2f7a9e8..25880d2441 100644 --- a/data/reusables/project-management/resync-automation.md +++ b/data/reusables/project-management/resync-automation.md @@ -1 +1 @@ -When you close a project board, any workflow automation configured for the project board will pause. If you reopen a project 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 "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[Closing a project board](/articles/closing-a-project-board)." +When you close a {% data variables.projects.projects_v1_board %}, any workflow automation configured for the {% data variables.projects.projects_v1_board %} will pause. 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 project. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)." diff --git a/data/reusables/project-management/select-project.md b/data/reusables/project-management/select-project.md index 2460ba9441..20b4b10488 100644 --- a/data/reusables/project-management/select-project.md +++ b/data/reusables/project-management/select-project.md @@ -1,2 +1,2 @@ -1. In the projects list, click the name of the project board. +1. In the projects list, click the name of the {% data variables.projects.projects_v1_board %}. ![Select project](/assets/images/help/projects/select-project.png) diff --git a/data/reusables/project-management/use-automated-template.md b/data/reusables/project-management/use-automated-template.md index 889f232af9..851220db4c 100644 --- a/data/reusables/project-management/use-automated-template.md +++ b/data/reusables/project-management/use-automated-template.md @@ -1 +1 @@ -You can use a project board template to create a project board with automation already configured. For more information, see "[About project boards](/articles/about-project-boards#templates-for-project-boards)." +You can use a {% data variables.projects.projects_v1_board %} template to create a {% data variables.projects.projects_v1_board %} with automation already configured. For more information, see "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards#templates-for-project-boards)." diff --git a/data/reusables/projects/about-workflows.md b/data/reusables/projects/about-workflows.md index 5c78c53bc5..d2472004a5 100644 --- a/data/reusables/projects/about-workflows.md +++ b/data/reusables/projects/about-workflows.md @@ -1,3 +1,3 @@ -Projects (beta) includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed. +{% data variables.product.prodname_projects_v2 %} includes built-in workflows that you can use to update the **Status** of items based on certain events. For example, you can automatically set the status to **Todo** when an item is added to your project or set the status to **Done** when an issue is closed. When your project initializes, two workflows are enabled by default: When issues or pull requests in your project are closed, their status is set to **Done**, and when pull requests in your project are merged, their status is set to **Done**. diff --git a/data/reusables/projects/access-insights.md b/data/reusables/projects/access-insights.md index baa180aa23..e211db1d89 100644 --- a/data/reusables/projects/access-insights.md +++ b/data/reusables/projects/access-insights.md @@ -1,8 +1,3 @@ 1. Navigate to your project. 2. In the top-right, to access insights, click {% octicon "graph" aria-label="the graph icon" %}. - - {% note %} - - **Note:** This feature is currently in a private preview and only available for some organizations. If the {% octicon "graph" aria-label="the graph icon" %} icon is not displayed in your project, insights is not yet enabled for your organization. - - {% endnote %} + ![Screenshot showing the insights icon](/assets/images/help/projects-v2/insights-button.png) diff --git a/data/reusables/projects/add-draft-issue.md b/data/reusables/projects/add-draft-issue.md new file mode 100644 index 0000000000..1daf1f11d3 --- /dev/null +++ b/data/reusables/projects/add-draft-issue.md @@ -0,0 +1,4 @@ +{% data reusables.projects.add-item-bottom-row %} +1. Type your idea, then press **Enter**. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-draft-issue.png) +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**. \ No newline at end of file diff --git a/data/reusables/projects/add-item-bottom-row.md b/data/reusables/projects/add-item-bottom-row.md new file mode 100644 index 0000000000..2a9b0070b6 --- /dev/null +++ b/data/reusables/projects/add-item-bottom-row.md @@ -0,0 +1,2 @@ +1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}. + ![Screenshot showing the bottom row to add an item](/assets/images/help/projects-v2/add-item.png) \ No newline at end of file diff --git a/data/reusables/projects/add-item-via-paste.md b/data/reusables/projects/add-item-via-paste.md new file mode 100644 index 0000000000..b2da1184db --- /dev/null +++ b/data/reusables/projects/add-item-via-paste.md @@ -0,0 +1,4 @@ +{% data reusables.projects.add-item-bottom-row %} +1. Paste the URL of the issue or pull request. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/paste-url-to-add.png) +3. To add the issue or pull request, press Return. \ No newline at end of file diff --git a/data/reusables/projects/bulk-add.md b/data/reusables/projects/bulk-add.md new file mode 100644 index 0000000000..a29d71e942 --- /dev/null +++ b/data/reusables/projects/bulk-add.md @@ -0,0 +1,6 @@ +1. Optionally, to change the repository, click the dropdown and select a repository. You can also search for specific issues and pull requests. + ![Screenshot showing repository dropdown](/assets/images/help/projects-v2/add-bulk-select-repo.png) +1. Select the issues and pull requests you want to add. + ![Screenshot showing selecting issues and pull requests to add](/assets/images/help/projects-v2/add-bulk-select-issues.png) +1. Click **Add selected items**. + ![Screenshot showing "add selected items" button](/assets/images/help/projects-v2/add-bulk-save.png) \ No newline at end of file diff --git a/data/reusables/projects/create-project.md b/data/reusables/projects/create-project.md index 7aba696394..21895e063e 100644 --- a/data/reusables/projects/create-project.md +++ b/data/reusables/projects/create-project.md @@ -1,8 +1,9 @@ -1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization. -1. Click {% octicon "table" aria-label="The project icon" %} **Projects**. -1. Select the **New project** drop-down menu and click **New project (Beta)**. - - ![New project](/assets/images/help/issues/new_project_beta.png) -1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +1. Under your organization name, click {% octicon "table" aria-label="The project icon" %} **Projects**. + ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png) +1. Click **New project**. + ![Screenshot showing New project button](/assets/images/help/projects-v2/new-project-button.png) +1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**. ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) diff --git a/data/reusables/projects/create-user-project.md b/data/reusables/projects/create-user-project.md index 1273840d38..1589d98fa5 100644 --- a/data/reusables/projects/create-user-project.md +++ b/data/reusables/projects/create-user-project.md @@ -1,7 +1,8 @@ -1. On any {% data variables.product.product_name %} page, click on your avatar, then select **Your projects**. -1. Select the **New project** drop-down menu and click **New project (Beta)**. - - ![New project](/assets/images/help/issues/new_project_beta.png) -1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. +{% data reusables.profile.access_profile %} +1. On your profile, click {% octicon "table" aria-label="The project icon" %} **Projects**. + ![Screenshot showing the 'Projects' tab](/assets/images/help/projects-v2/tab-projects.png) +1. Click **New project**. + ![New project](/assets/images/help/projects-v2/new-project-button.png) +1. When prompted to select a template, click a template or, to start with an empty project, click **Table** or **Board**. Then, click **Create**. ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) diff --git a/data/reusables/projects/enable-basic-workflow.md b/data/reusables/projects/enable-basic-workflow.md index 92bb137381..48742816af 100644 --- a/data/reusables/projects/enable-basic-workflow.md +++ b/data/reusables/projects/enable-basic-workflow.md @@ -1,7 +1,13 @@ 1. Navigate to your project. 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) 1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. + ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) 1. Under **Default workflows**, click on the workflow that you want to edit. + ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) 1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. + ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) 1. Next to **Set**, choose the value that you want to set the status to. + ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) 1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. + ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) diff --git a/data/reusables/projects/migrate-project-steps.md b/data/reusables/projects/migrate-project-steps.md index d1cacc98ee..8a09fb41d1 100644 --- a/data/reusables/projects/migrate-project-steps.md +++ b/data/reusables/projects/migrate-project-steps.md @@ -1,7 +1,7 @@ 1. Next to the project you want to migrate, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. -1. In the menu, click **Migrate to beta**. - ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-to-beta.png) +1. In the menu, click **Migrate**. + ![Screenshot showing migrate option](/assets/images/help/issues/migrate-menu-item.png) 1. In the the popup, select what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use. - ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-option.png) + ![Screenshot showing migrate modal](/assets/images/help/issues/migrate-option.png) 1. In the bottom right of the popup, click **Start migration**. - ![Screenshot showing migrate to beta option](/assets/images/help/issues/migrate-start.png) + ![Screenshot showing start migration button](/assets/images/help/issues/migrate-start.png) diff --git a/data/reusables/projects/new-field.md b/data/reusables/projects/new-field.md new file mode 100644 index 0000000000..60284f6dc2 --- /dev/null +++ b/data/reusables/projects/new-field.md @@ -0,0 +1,6 @@ +1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}. + ![Screenshot showing new field button](/assets/images/help/projects-v2/new-field-button.png) +1. Click **New field**. + ![Screenshot showing new field menu item](/assets/images/help/projects-v2/new-field-menu-item.png) +1. Type the name of your new field. + ![Screenshot showing the field name](/assets/images/help/projects-v2/new-field-name.png) \ No newline at end of file diff --git a/data/reusables/projects/new-view.md b/data/reusables/projects/new-view.md new file mode 100644 index 0000000000..cf52a8ce1a --- /dev/null +++ b/data/reusables/projects/new-view.md @@ -0,0 +1,2 @@ +1. To the right of your existing views, click **New view** + ![Screenshot showing the column field menu](/assets/images/help/projects-v2/new-view.png) \ No newline at end of file diff --git a/data/reusables/projects/open-item-menu.md b/data/reusables/projects/open-item-menu.md new file mode 100644 index 0000000000..5c9c7fc258 --- /dev/null +++ b/data/reusables/projects/open-item-menu.md @@ -0,0 +1 @@ +1. Select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout). \ No newline at end of file diff --git a/data/reusables/projects/open-view-menu.md b/data/reusables/projects/open-view-menu.md new file mode 100644 index 0000000000..6cf3045784 --- /dev/null +++ b/data/reusables/projects/open-view-menu.md @@ -0,0 +1,2 @@ +1. Click {% octicon "triangle-down" aria-label="the drop-down icon" %} next to the name of the currently open view. + ![Screenshot showing the view menu icon](/assets/images/help/projects-v2/view-menu-icon.png) \ No newline at end of file diff --git a/data/reusables/projects/project-description.md b/data/reusables/projects/project-description.md index 47c4f2e4fb..832430e468 100644 --- a/data/reusables/projects/project-description.md +++ b/data/reusables/projects/project-description.md @@ -2,9 +2,12 @@ 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**. + ![Screenshot showing the 'Add my description' settings](/assets/images/help/projects-v2/edit-description.png) 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 "[Basic writing and formatting syntax](/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" %}. + ![Screenshot showing editing a project's README](/assets/images/help/projects-v2/edit-readme.png) 1. To save changes to your README, click **Save**. + ![Screenshot showing the 'Save' button for a project's README](/assets/images/help/projects-v2/save-readme-button.png) 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. diff --git a/data/reusables/projects/project-settings.md b/data/reusables/projects/project-settings.md index 4c244857b3..7b23c69d75 100644 --- a/data/reusables/projects/project-settings.md +++ b/data/reusables/projects/project-settings.md @@ -1,3 +1,5 @@ 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 "gear" aria-label="The gear icon" %} **Settings** to access the project settings. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. + ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) diff --git a/data/reusables/projects/project_boards_old.md b/data/reusables/projects/project_boards_old.md index 48f8e3c287..4eed540e87 100644 --- a/data/reusables/projects/project_boards_old.md +++ b/data/reusables/projects/project_boards_old.md @@ -3,9 +3,8 @@ {% note %} **Notes:** - -* Projects (beta), the all-new projects experience, is now available. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and "[Migrating your project to Projects (beta)](/issues/trying-out-the-new-projects-experience/migrating-your-project)." -* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a beta project board instead. +* {% data variables.product.prodname_projects_v2 %}, the all-new projects experience, is now available. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" and for information about migrating your {% data variables.projects.projects_v1_board %}, see "[Migrating from {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)." +* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. If you're unable to create a classic project board, create a project board instead. {% endnote %} diff --git a/data/reusables/projects/projects-api.md b/data/reusables/projects/projects-api.md index 885e6f0683..c04b944049 100644 --- a/data/reusables/projects/projects-api.md +++ b/data/reusables/projects/projects-api.md @@ -3,8 +3,8 @@ **Notes:** -* This API only applies to project boards. Projects (beta) can be managed with the GraphQL API. For more information, see "[Using the API to manage projects (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)." -* You can only create a new classic project board for an organization, user, or repository that already has at least one classic project board. +* This API only applies to {% data variables.product.prodname_projects_v1 %}. {% data variables.product.prodname_projects_v2 %} can be managed with the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." +* You can only create a new {% data variables.projects.projects_v1_board %} for an organization, user, or repository that already has at least one {% data variables.projects.projects_v1_board %}. {% endnote %} {% endif %} diff --git a/data/reusables/projects/reopen-a-project.md b/data/reusables/projects/reopen-a-project.md index 916b1bcea1..c827c47e93 100644 --- a/data/reusables/projects/reopen-a-project.md +++ b/data/reusables/projects/reopen-a-project.md @@ -4,6 +4,8 @@ ![Screenshot showing project close button](/assets/images/help/issues/closed-projects-tab.png) 1. Click the project you want to reopen. 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. -1. In the menu, to access the project settings, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. + ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) 1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png) diff --git a/data/reusables/projects/save-view.md b/data/reusables/projects/save-view.md new file mode 100644 index 0000000000..8183c5054f --- /dev/null +++ b/data/reusables/projects/save-view.md @@ -0,0 +1,3 @@ +{% data reusables.projects.open-view-menu %} +1. Click **Save changes**. + ![Screenshot showing the save menu item](/assets/images/help/projects-v2/save-view.png) \ No newline at end of file diff --git a/data/reusables/projects/select-an-item.md b/data/reusables/projects/select-an-item.md new file mode 100644 index 0000000000..898a752d46 --- /dev/null +++ b/data/reusables/projects/select-an-item.md @@ -0,0 +1,5 @@ +1. Select the item. To select multiple items, do one of the following: + - Hold Command (Mac) or Ctrl (Windows/Linux) and click each item. + - Select an item then press Shift+↑ or Shift+↓ to select additional items above or below the selected item. + - Select an item then press Shift and click another item to select all items between the two items. + - With a row or item already selected, press Command+A (Mac) or Ctrl+A (Windows/Linux) to select all items in a column in a board layout or all items in a table layout. \ No newline at end of file diff --git a/data/reusables/webhooks/project_card_short_desc.md b/data/reusables/webhooks/project_card_short_desc.md index 6fe2904d9e..2e2ca0cf90 100644 --- a/data/reusables/webhooks/project_card_short_desc.md +++ b/data/reusables/webhooks/project_card_short_desc.md @@ -1 +1 @@ -Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. +Activity related to cards in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API. diff --git a/data/reusables/webhooks/project_column_short_desc.md b/data/reusables/webhooks/project_column_short_desc.md index 35d38e4101..a45a7e5759 100644 --- a/data/reusables/webhooks/project_column_short_desc.md +++ b/data/reusables/webhooks/project_column_short_desc.md @@ -1 +1 @@ -Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. +Activity related to columns in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API. diff --git a/data/reusables/webhooks/project_short_desc.md b/data/reusables/webhooks/project_short_desc.md index 2ae5d8be21..fe9313b6f4 100644 --- a/data/reusables/webhooks/project_short_desc.md +++ b/data/reusables/webhooks/project_short_desc.md @@ -1 +1 @@ -Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. +Activity related to {% data variables.projects.projects_v1_boards %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API. diff --git a/data/variables/product.yml b/data/variables/product.yml index b497ed3b50..e09b94fab3 100644 --- a/data/variables/product.yml +++ b/data/variables/product.yml @@ -85,6 +85,17 @@ prodname_codeql_cli: 'CodeQL CLI' codeql_cli_ghes_recommended_version: >- {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 %}2.7.6{% elsif ghes = 3.5 %}2.8.5{% elsif ghes = 3.6 %}2.9.4{% elsif ghae-issue-7470 %}2.8.5{% elsif ghae %}2.7.6{% endif %} +# Projects v2 +prodname_projects_v2: 'Projects' +prodname_projects_v1: >- + {% ifversion ghes or ghae %}project boards{% else %}projects (classic){% endif %} +prodname_projects_v1_caps: >- + {% ifversion ghes or ghae %}Project boards{% else %}Projects (classic){% endif %} +prodname_project_v1: >- + {% ifversion ghes or ghae %}project board{% else %}project (classic){% endif %} +prodname_project_v1_caps: >- + {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %} + # Apps, GitHub Marketplace, and integrations prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' diff --git a/data/variables/projects.yml b/data/variables/projects.yml new file mode 100644 index 0000000000..a34fe3d8b4 --- /dev/null +++ b/data/variables/projects.yml @@ -0,0 +1,15 @@ +projects_v2: 'projects' +projects_v2_caps: 'Projects' +project_v2: 'project' +project_v2_caps: 'Project' + +projects_v1_board: >- + {% ifversion ghes or ghae %}project board{% else %}classic project{% endif %} +projects_v1_board_caps: >- + {% ifversion ghes or ghae %}Project board{% else %}Classic project{% endif %} +projects_v1_boards: >- + {% ifversion ghes or ghae %}project boards{% else %}classic projects{% endif %} +projects_v1_boards_caps: >- + {% ifversion ghes or ghae %}Project boards{% else %}Classic projects{% endif %} + +command-palette-shortcut: 'Command+K (Mac) or Ctrl+K (Windows/Linux)'