From 02e9ed622ce703fee0effe89b158f67641c61608 Mon Sep 17 00:00:00 2001 From: Riley Broughten <101840513+rileybroughten@users.noreply.github.com> Date: Wed, 9 Apr 2025 09:06:38 -0700 Subject: [PATCH] Evolving GitHub Issues [GA] (#54869) Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- .../syntax-for-issue-forms.md | 6 ------ .../customizing-views-in-your-project/filtering-projects.md | 4 ---- .../managing-issue-types-in-an-organization.md | 2 -- .../planning-and-tracking-work-for-your-team-or-project.md | 2 -- .../using-issues/editing-an-issue.md | 2 -- content/rest/issues/sub-issues.md | 2 -- data/features/issue-types.yml | 2 +- data/features/issues-advanced-search.yml | 2 +- data/features/sub-issues.yml | 2 +- data/reusables/issues/release-stage.md | 3 --- 10 files changed, 3 insertions(+), 24 deletions(-) delete mode 100644 data/reusables/issues/release-stage.md diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md index 3b2a02024e..0460882351 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md @@ -35,12 +35,6 @@ body: You can set the following top-level keys for each issue form. -{% ifversion issue-types %} - -{% data reusables.issues.release-stage %} - -{% endif %} - | Key | Description | Required | Type | | :-- | :-- | :-- | :-- | | `name` | A name for the issue form template. Must be unique from all other templates, including Markdown templates. | Required | String | 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 index 3243957bc5..a65011decf 100644 --- 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 @@ -233,8 +233,6 @@ You can also use a * as a wildcard. If your organization uses issue types, you can filter for particular types. -{% data reusables.issues.release-stage %} - | Qualifier | Example | ---------- | ------------- | type:"ISSUE TYPE" | **type:"bug"** will show issues with the "bug" type. @@ -247,8 +245,6 @@ If your organization uses issue types, you can filter for particular types. You can filter your sub-issues by their parent issue. -{% data reusables.issues.release-stage %} - | Qualifier | Example | ---------- | ------------- | parent-issue:OWNER/REPO#ISSUE NUMBER | **parent-issue:octocat/game#4** will show issues with issue #4 in octocat/game as their parent issue. diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md b/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md index 480e58786b..73b07b7be0 100644 --- a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md +++ b/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md @@ -10,8 +10,6 @@ shortTitle: 'Managing issue types' permissions: 'Organization owners can modify issue types.' --- -{% data reusables.issues.release-stage %} - You can use issue types to classify and manage different types of issues across your organization. You can create up to {% data variables.projects.issue_type_limit %} issue types that your organization members can apply to issues, making it easier for you and your members to find issues and plan work. Default issue types are included in every organization, but these can edited, disabled, or deleted. The default types are task, bug, and feature. diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md index 75797d201d..5f6b8fe952 100644 --- a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -88,8 +88,6 @@ Below we have added a task list to our Project Octocat issue, breaking it down i ### Breaking down your work with sub-issues -{% data reusables.issues.release-stage %} - {% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues). {% endif %} diff --git a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md index 4eb1fb4fa2..25bd5a6c6f 100644 --- a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md +++ b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md @@ -42,8 +42,6 @@ You can also make changes to the issue description. The edit history is availabl ## Adding or changing the issue type -{% data reusables.issues.release-stage %} - You can add an issue type or make changes to an existing issue type. 1. Navigate to the issue you want to edit. diff --git a/content/rest/issues/sub-issues.md b/content/rest/issues/sub-issues.md index 07cce607c4..f7d9de205c 100644 --- a/content/rest/issues/sub-issues.md +++ b/content/rest/issues/sub-issues.md @@ -11,6 +11,4 @@ autogenerated: rest allowTitleToDifferFromFilename: true --- -{% data reusables.issues.release-stage %} - diff --git a/data/features/issue-types.yml b/data/features/issue-types.yml index 8cd17a8c69..4ab0d81619 100644 --- a/data/features/issue-types.yml +++ b/data/features/issue-types.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.16' + ghes: '>=3.18' diff --git a/data/features/issues-advanced-search.yml b/data/features/issues-advanced-search.yml index 8378b523c6..fe3b59f642 100644 --- a/data/features/issues-advanced-search.yml +++ b/data/features/issues-advanced-search.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.16' + ghes: '>=3.18' diff --git a/data/features/sub-issues.yml b/data/features/sub-issues.yml index a4c0c0be6d..38e21ad6c9 100644 --- a/data/features/sub-issues.yml +++ b/data/features/sub-issues.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.17' + ghes: '>=3.18' diff --git a/data/reusables/issues/release-stage.md b/data/reusables/issues/release-stage.md deleted file mode 100644 index 5a7769e0d4..0000000000 --- a/data/reusables/issues/release-stage.md +++ /dev/null @@ -1,3 +0,0 @@ ->[!NOTE] ->Issue types, sub-issues, and advanced issue search are currently in {% data variables.release-phases.public_preview %} for organizations. See the [GitHub Blog](https://github.blog/changelog/2025-01-13-evolving-github-issues-public-preview/). -