Evolving GitHub Issues [GA] (#54869)
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
This commit is contained in:
@@ -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 |
|
||||
|
||||
@@ -233,8 +233,6 @@ You can also use a <code>*</code> as a wildcard.
|
||||
|
||||
If your organization uses issue types, you can filter for particular types.
|
||||
|
||||
{% data reusables.issues.release-stage %}
|
||||
|
||||
| Qualifier | Example
|
||||
| ---------- | -------------
|
||||
| <code>type:"<em>ISSUE TYPE</em>" | **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
|
||||
| ---------- | -------------
|
||||
| <code>parent-issue:<em>OWNER/REPO#ISSUE NUMBER</em></code> | **parent-issue:octocat/game#4** will show issues with issue #4 in octocat/game as their parent issue.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -11,6 +11,4 @@ autogenerated: rest
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.issues.release-stage %}
|
||||
|
||||
<!-- Content after this section is automatically generated -->
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.16'
|
||||
ghes: '>=3.18'
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.16'
|
||||
ghes: '>=3.18'
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.17'
|
||||
ghes: '>=3.18'
|
||||
|
||||
@@ -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/).
|
||||
<!-- also update the tip in search-github/searching-on-github/searching-issues-and-pull-requests -->
|
||||
Reference in New Issue
Block a user