Hack week 2025: remove unneeded FBV instances (20) - Projects (#54012)

mchammer01 · web-flow · commit 857620314a5a · 2025-01-21T07:26:16.000Z
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md
@@ -40,15 +40,13 @@ Projects also have a limit on the number of archived items they can contain. You
 ## Configuring automatic archiving in your project
 
 {% data reusables.projects.access-workflows %}
-1. In the "Default workflows" list, click **Auto-archive items**.{% ifversion projects-v2-workflows-ui-refresh %}
+1. In the "Default workflows" list, click **Auto-archive items**.
 1. In the top right, click **Edit**.
 
    ![Screenshot showing a project's menu bar. The "Edit" button is highlighted with an orange rectangle.](/assets/images/help/projects-v2/workflow-start-editing.png)
-   {% else %}
-1. Next to **When**, check the item type(s) that you want to automatically archive.{% endif %}
-1. In the "Filters" field, type the filter criteria you want to use to automatically archive items. You can only use the `is`, `reason`, and `updated` filters.{% ifversion projects-v2-workflows-ui-refresh %}
-1. To save your changes and enable the workflow, click **Save and turn on workflow**.{% else %}
-1. If the workflow is disabled, click the toggle next to **Off** to enable the workflow.{% endif %}
+
+1. In the "Filters" field, type the filter criteria you want to use to automatically archive items. You can only use the `is`, `reason`, and `updated` filters.
+1. To save your changes and enable the workflow, click **Save and turn on workflow**.
 
 ## Further reading
 
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/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
@@ -395,7 +395,7 @@ gh api graphql -f query='
             nodes{
               id
               fieldValues(first: 8) {
-                nodes{                
+                nodes{
                   ... on ProjectV2ItemFieldTextValue {
                     text
                     field {
@@ -420,9 +420,9 @@ gh api graphql -f query='
                       }
                     }
                   }
-                }              
+                }
               }
-              content{              
+              content{
                 ... on DraftIssue {
                   title
                   body
@@ -574,7 +574,7 @@ gh api graphql -f query='
   mutation {
     updateProjectV2(
       input: {
-        projectId: "PROJECT_ID", 
+        projectId: "PROJECT_ID",
         title: "Project title",
         public: false,
         readme: "# Project README\n\nA long description",
@@ -618,8 +618,8 @@ gh api graphql -f query='
         projectId: "PROJECT_ID"
         itemId: "ITEM_ID"
         fieldId: "FIELD_ID"
-        value: { 
-          text: "Updated text"        
+        value: {
+          text: "Updated text"
         }
       }
     ) {
@@ -673,8 +673,8 @@ gh api graphql -f query='
         projectId: "PROJECT_ID"
         itemId: "ITEM_ID"
         fieldId: "FIELD_ID"
-        value: { 
-          singleSelectOptionId: "OPTION_ID"        
+        value: {
+          singleSelectOptionId: "OPTION_ID"
         }
       }
     ) {
@@ -717,8 +717,8 @@ gh api graphql -f query='
         projectId: "PROJECT_ID"
         itemId: "ITEM_ID"
         fieldId: "FIELD_ID"
-        value: { 
-          iterationId: "ITERATION_ID"        
+        value: {
+          iterationId: "ITERATION_ID"
         }
       }
     ) {
@@ -826,10 +826,6 @@ gh api graphql -f query='
 
 {% endcli %}
 
-{% ifversion projects-v2-webhooks %}
-
 ## 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 [AUTOTITLE](/webhooks-and-events/webhooks/about-webhooks). To learn more about the `projects_v2_item` webhook event, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item).
-
-{% endif %}
diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md b/content/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md
@@ -3,7 +3,9 @@ title: 'Copying an existing {% data variables.projects.project_v2 %}'
 shortTitle: Copying a project
 intro: You can use an existing project as a template by copying it.
 versions:
-  feature: projects-v2-copy-a-project
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 type: tutorial
 topics:
   - Projects
@@ -16,7 +18,7 @@ You can copy an existing project and use it as a template to save time configuri
 
 When you copy a project, the new project will contain the same {% data reusables.projects.what-gets-copied %}. {% ifversion projects-v2-org-templates-improvements %}The new project will not contain the original project's items, collaborators, or team and repository links.{% else %}The new project will not contain the original project's items, workflows, insights, collaborators, or team and repository links.{% endif %}
 
-{% ifversion projects-v2-org-templates %}{% data reusables.projects.org-templates %}{% endif %}
+{% data reusables.projects.org-templates %}
 
 ## Copying an existing project
 
@@ -27,9 +29,9 @@ When you copy a project, the new project will contain the same {% data reusables
 
 1. In the menu, click **{% octicon "copy" aria-hidden="true" %} Make a copy**.
 1. Optionally, if you want all draft issues to be copied with the project, in the "Make a copy" dialog, select **Draft issues will be copied if selected**.{%- ifversion projects-v2-org-templates-improvements %}{%- else %}
-  
+
    ![Screenshot showing the "Make a copy" form.](/assets/images/help/projects-v2/copy-project-form.png)
-  
+
 {%- endif %}
 1. Under "Owner", select either the organization that will own the new project or your personal account.
 1. Under "New project name", type the name of the new project.
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
@@ -13,17 +13,13 @@ 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.
 
-{% ifversion projects-v2-copy-a-project %}
-
 You can also choose to use an existing project as a template and copy the views and custom fields to a new project. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project).
 
-{% endif %}
-
 ## Creating a project
 
 ### Creating an organization project
 
-Organization projects can track issues and pull requests from the organization's repositories. {% ifversion projects-v2-org-templates %}{% data reusables.projects.org-templates %}{% endif %}
+Organization projects can track issues and pull requests from the organization's repositories. {% data reusables.projects.org-templates %}
 
 {% data reusables.projects.create-project %}
 
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md
@@ -15,8 +15,6 @@ topics:
 
 For more information about changing a view to use the board layout, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view#changing-the-project-layout).
 
-{% ifversion projects-v2-column-limits %}
-
 ## Setting a limit on the number of items in a column
 
 You can set a limit for the number of cards in a particular column in a board layout. Setting a limit does not restrict anyone from adding cards that would exceed the column's limit, nor does it restrict any automations from adding cards. Column limits are unique to each view in your project.
@@ -30,8 +28,6 @@ The current count of cards and the column's limit is displayed at the top of the
 1. Optionally, to remove the limit, clear the entry.
 1. Click **Save**.
 
-{% endif %}
-
 ## Showing and hiding fields
 
 {% data reusables.projects.customize.show-hide-field %}
@@ -44,8 +40,6 @@ In the board layout, you choose any single select or iteration field for your co
 1. Click **{% octicon "columns" aria-hidden="true" %} Column field**.
 1. Click the field you want to use.
 
-{% ifversion projects-v2-column-visibility %}
-
 ## Showing and hiding columns in board layout
 
 In the board layout, you can choose which columns to display. The available columns are made up of the contents of your selected column field.
@@ -55,7 +49,6 @@ In the board layout, you can choose which columns to display. The available colu
    ![Screenshot of a board layout scrolled to the very right. The "Add a new column to the board" button is highlighted with an orange outline.](/assets/images/help/projects-v2/board-add-column.png)
 
 1. Select the columns you want to show.
-{% endif %}
 
 {% ifversion projects-v2-slice-panel %}
 
@@ -65,8 +58,6 @@ In the board layout, you can choose which columns to display. The available colu
 
 {% endif %}
 
-{% ifversion projects-v2-consistent-sorting %}
-
 ## Sorting by field values
 
 You can sort items by a field value.
@@ -76,8 +67,6 @@ You can sort items by a field value.
 
 {% data reusables.projects.customize.sort %}
 
-{% endif %}
-
 {% ifversion projects-v2-swimlanes %}
 
 ## Grouping by field values
@@ -90,10 +79,6 @@ You can use a custom field value to group items and create horizontal sections o
 
 {% endif %}
 
-{% ifversion projects-v2-numeric-summary %}
-
 ## Showing the sum of a number field
 
 {% data reusables.projects.customize.sum %}
-
-{% endif %}
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md
@@ -28,8 +28,6 @@ You can set the date or iteration fields that your roadmap will use to position
 1. Optionally, to create a new date or iteration field, click **{% octicon "plus" aria-hidden="true" %} New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
 1. Select a date or iteration field for "Start date" and "Target date."
 
-{% ifversion projects-v2-roadmap-markers %}
-
 ## Setting vertical markers
 
 You can configure vertical markers on a roadmap to show your iterations, the dates of items in your project, and the milestones associated with items in your project.
@@ -40,8 +38,6 @@ You can configure vertical markers on a roadmap to show your iterations, the dat
 
 1. In the menu, select which markers you want to display on your roadmap.
 
-{% endif %}
-
 ## Setting the zoom level
 
 You can choose the density of items on your roadmap. You can zoom in to show one month at a time or, for a greater overview, you can zoom out to show a quarter of a year or a full year.
@@ -60,36 +56,18 @@ You can choose the density of items on your roadmap. You can zoom in to show one
 
 {% endif %}
 
-{% ifversion projects-v2-consistent-sorting %}
-
 ## Sorting by field values
 
 You can sort items by a field value.
 
 {% data reusables.projects.customize.sort %}
 
-{% endif %}
-
-{% ifversion projects-v2-roadmap-markers %}{% else %}
-
-## Showing and hiding fields
-
-When you show and hide fields on the roadmap layout, you define which fields are shown when the side panel opens. This setting will not affect the information visible on the roadmap layout.
-
-{% data reusables.projects.customize.show-hide-field %}
-
-{% endif %}
-
 ## Grouping by field values
 
 You can group items by a custom field value.
 
 {% data reusables.projects.customize.group-fields %}
 
-{% ifversion projects-v2-numeric-summary %}
-
 ## Showing the sum of a number field
 
 {% data reusables.projects.customize.sum %}
-
-{% endif %}
diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md
@@ -65,19 +65,8 @@ You can change the order of rows.
 
 You can sort items by a field value.
 
-{% ifversion projects-v2-consistent-sorting %}{% else %}
-
-> [!NOTE]
-> When a table is sorted, you cannot manually reorder rows.
-
-{% endif %}
-
 {% data reusables.projects.customize.sort %}
 
-{% ifversion projects-v2-numeric-summary %}
-
 ## Showing the sum of a number field
 
 {% data reusables.projects.customize.sum %}
-
-{% endif %}
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
@@ -21,7 +21,7 @@ To get started and create a project, see [AUTOTITLE](/issues/planning-and-tracki
 
 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.
 
-To learn more about managing items in your project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project){% ifversion projects-v2-bulk-table-editing %} and [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project){% endif %}.
+To learn more about managing items in your project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project) and [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project).
 
 ### Adding metadata to your items
 
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
@@ -26,12 +26,8 @@ When you add an issue or pull request to your project, an event will be added to
 
 {% endif %}
 
-{% ifversion projects-v2-bulk-table-editing %}
-
 For more information about making bulk changes to your items after adding them, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project).
 
-{% endif %}
-
 ### Automatically adding issues and pull requests
 
 You can configure a built-in workflow to automatically add issues and pull requests from a repository when they meet specific filter criteria. For more information about configuring a workflow, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically).
@@ -95,16 +91,12 @@ You can use the command palette when viewing your project to quickly add items.
 1. Start typing "Add items" and press <kbd>Return</kbd>.
 {% data reusables.projects.bulk-add %}
 
-{% ifversion projects-v2-create-issue-modal %}
-
 ## Creating issues
 
 {% data reusables.projects.about-issue-modal %}
 
 {% data reusables.projects.create-issue-modal %}
 
-{% endif %}
-
 ## 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.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project.md b/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project.md
@@ -3,7 +3,9 @@ title: 'Editing items in your {% data variables.projects.project_v2 %}'
 shortTitle: Editing items
 intro: 'There are several methods you can use within your {% data variables.projects.project_v2 %} to quickly make changes to multiple items.'
 versions:
-  feature: projects-v2-bulk-table-editing
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 type: tutorial
 topics:
   - Projects
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -27,18 +27,10 @@ You can control access to your project by setting permissions for particular ind
 
 ### Managing access for everyone in your organization
 
-{% ifversion projects-v2-default-base-permission %}
-
 You can manage access for everyone in your organization to a particular project by changing the project's base permission. Changes to the base permission only affect organization members who are not organization owners and who are not granted individual access.
 
 You can also configure the default base permission at the organization-level for new projects and projects that haven't yet had a base permission configured. For more information about setting your organization's base permission for projects, see [AUTOTITLE](/organizations/managing-organization-settings/managing-base-permissions-for-projects).
 
-{% else %}
-
-The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
-
-{% endif %}
-
 {% data reusables.projects.project-settings %}
 1. Click **Manage access**.
 1. Under **Base role**, select the default role.
diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md
@@ -3,7 +3,9 @@ title: 'Managing {% data variables.projects.project_v2 %} templates in your orga
 shortTitle: 'Managing templates'
 intro: 'You can {% ifversion projects-v2-org-templates-improvements %}create templates or {% endif %}set projects as templates in your organization, allowing other people to select your template as the base for projects they create.'
 versions:
-  feature: projects-v2-org-templates
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
 type: tutorial
 permissions: 'People with admin permissions for a project in an organization can set the project as a template. People with admin or write permissions for a project in an organization can copy the project and set the copied project as a template.'
 topics:
diff --git a/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md b/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md
@@ -1,7 +1,7 @@
 ---
 title: About single select fields
 shortTitle: About single select fields
-intro: 'You can create single select fields with multiple options{% ifversion projects-v2-colorful-selects %}, each with a description and a color,{% endif %} that can be selected from a dropdown menu.'
+intro: 'You can create single select fields with multiple options, each with a description and a color, that can be selected from a dropdown menu.'
 versions:
   feature: projects-v2
 type: tutorial
@@ -25,8 +25,6 @@ Single select fields can contain up to 50 options.
 
 ## Editing a single select field
 
-{% ifversion projects-v2-colorful-selects %}
-
 You can set descriptions and colors for each of your single select options.
 
 1. Access your project's settings.
@@ -41,13 +39,3 @@ You can set descriptions and colors for each of your single select options.
 
 1. Optionally, under **Description**, type a description for this option.
 1. Click **Save** to save your changes.
-
-{% else %}
-
-{% data reusables.projects.project-settings %}
-1. Click the name of the single select field you want to adjust.
-1. Edit existing options or click **Add option**.
-1. Optionally, to delete an option, click {% octicon "x" aria-label="Remove option" %}.
-1. Click **Save options**.
-
-{% endif %}
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md
diff --git a/content/organizations/managing-organization-settings/managing-base-permissions-for-projects.md b/content/organizations/managing-organization-settings/managing-base-permissions-for-projects.md
diff --git a/data/reusables/projects/about-board-layout.md b/data/reusables/projects/about-board-layout.md
diff --git a/data/reusables/projects/about-roadmap-layout.md b/data/reusables/projects/about-roadmap-layout.md
diff --git a/data/reusables/projects/create-project.md b/data/reusables/projects/create-project.md
diff --git a/data/reusables/projects/create-user-project.md b/data/reusables/projects/create-user-project.md
