.github/ISSUE_TEMPLATE: initial common fields sync
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
@@ -9,20 +9,22 @@ body:
|
||||
value: |
|
||||
Please fill in each section completely, and [search in GitHub](https://github.com/backstage/backstage/search?type=Issues)
|
||||
before reporting a new bug in order to avoid duplicates. Thank you!
|
||||
- type: checkboxes
|
||||
id: issue-labels
|
||||
# This field is managed by .common.yaml
|
||||
- id: issue-labels
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: '📜 Issue Labels'
|
||||
options:
|
||||
- label: 'Please familiarize yourself with the issue labels used in this project: [LABELS.md](https://github.com/backstage/backstage/blob/master/LABELS.md)'
|
||||
required: true
|
||||
- type: textarea
|
||||
id: search-terms
|
||||
# This field is managed by .common.yaml
|
||||
- id: search-terms
|
||||
type: textarea
|
||||
attributes:
|
||||
label: '🔎 Search Terms'
|
||||
render: plain
|
||||
description: |
|
||||
What search terms did you use when trying to find an existing bug report?
|
||||
What search terms did you use when trying to find an existing feature proposal?
|
||||
placeholder: |
|
||||
List of keywords you searched for before creating this issue. Write them down here so that others can find this bug more easily and help provide feedback.
|
||||
|
||||
@@ -38,11 +40,12 @@ body:
|
||||
## Defining the bug
|
||||
|
||||
Defining the bug accurately will help ensure that it is identified and fixed correctly.
|
||||
- type: dropdown
|
||||
id: project-area
|
||||
# This field is managed by .common.yaml
|
||||
- id: project-area
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: '🗃️ Project Area'
|
||||
description: What area of the project do you think this bug is related to? This will help find an owner for the issue faster.
|
||||
description: What area of the project would this feature be related to? This will help find an owner for the issue faster.
|
||||
options:
|
||||
- Unknown
|
||||
- Auditor
|
||||
@@ -135,8 +138,9 @@ body:
|
||||
3. Scroll down to '....'"
|
||||
validations:
|
||||
required: false
|
||||
- type: checkboxes
|
||||
id: read-code-of-conduct
|
||||
# This field is managed by .common.yaml
|
||||
- id: read-code-of-conduct
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: 'Have you read the Code of Conduct?'
|
||||
options:
|
||||
|
||||
@@ -10,18 +10,20 @@ body:
|
||||
This template is used to report issues in the Backstage documentation.
|
||||
|
||||
The documentation at [backstage.io](https://backstage.io) is only updated when a new release is made. Before reporting an issue here, please check that the issue also exists in the ["next"](https://backstage.io/docs/next/overview/what-is-backstage) version of the documentation, which you can switch to in the top-right dropdown menu.
|
||||
- type: checkboxes
|
||||
id: issue-labels
|
||||
# This field is managed by .common.yaml
|
||||
- id: issue-labels
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: '📜 Issue Labels'
|
||||
options:
|
||||
- label: 'Please familiarize yourself with the issue labels used in this project: [LABELS.md](https://github.com/backstage/backstage/blob/master/LABELS.md)'
|
||||
required: true
|
||||
- type: dropdown
|
||||
id: project-area
|
||||
# This field is managed by .common.yaml
|
||||
- id: project-area
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: '🗃️ Project Area'
|
||||
description: What area of the project do you think this bug is related to? This will help find an owner for the issue faster.
|
||||
description: What area of the project would this feature be related to? This will help find an owner for the issue faster.
|
||||
options:
|
||||
- Unknown
|
||||
- Auditor
|
||||
@@ -71,8 +73,9 @@ body:
|
||||
description: Describe the problem you have found in the docs.
|
||||
placeholder: |
|
||||
Please provide links to the specific pages and sections that need to be corrected and describe the problem you have found.
|
||||
- type: checkboxes
|
||||
id: read-code-of-conduct
|
||||
# This field is managed by .common.yaml
|
||||
- id: read-code-of-conduct
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: 'Have you read the Code of Conduct?'
|
||||
options:
|
||||
|
||||
@@ -8,15 +8,17 @@ body:
|
||||
attributes:
|
||||
value: |
|
||||
This template lets you highlight maintenance tasks that need special consideration, such as tricky version bumps or migrations.
|
||||
- type: checkboxes
|
||||
id: issue-labels
|
||||
# This field is managed by .common.yaml
|
||||
- id: issue-labels
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: '📜 Issue Labels'
|
||||
options:
|
||||
- label: 'Please familiarize yourself with the issue labels used in this project: [LABELS.md](https://github.com/backstage/backstage/blob/master/LABELS.md)'
|
||||
required: true
|
||||
- type: textarea
|
||||
id: search-terms
|
||||
# This field is managed by .common.yaml
|
||||
- id: search-terms
|
||||
type: textarea
|
||||
attributes:
|
||||
label: '🔎 Search Terms'
|
||||
render: plain
|
||||
@@ -28,8 +30,9 @@ body:
|
||||
e.g. "catalog github rate limited", "http root service configurer", "scaffolder template include", "entity card title"
|
||||
validations:
|
||||
required: true
|
||||
- type: dropdown
|
||||
id: project-area
|
||||
# This field is managed by .common.yaml
|
||||
- id: project-area
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: '🗃️ Project Area'
|
||||
description: What area of the project would this feature be related to? This will help find an owner for the issue faster.
|
||||
@@ -73,15 +76,17 @@ body:
|
||||
Explain what level of prioritization this task should receive. Are there any particular benefits provided in newer versions in case of a version bump, or any security vulnerabilities that can be removed?
|
||||
|
||||
Also list any important dates or deadlines, which as current versions reaching end of life, or release dates for stable releases.
|
||||
- type: checkboxes
|
||||
id: read-code-of-conduct
|
||||
# This field is managed by .common.yaml
|
||||
- id: read-code-of-conduct
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: 'Have you read the Code of Conduct?'
|
||||
options:
|
||||
- label: 'I have read the [Code of Conduct](https://github.com/backstage/backstage/blob/master/CODE_OF_CONDUCT.md)'
|
||||
required: true
|
||||
- type: dropdown
|
||||
id: willing-to-submit-pr
|
||||
# This field is managed by .common.yaml
|
||||
- id: willing-to-submit-pr
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: Are you willing to submit PR?
|
||||
description: This is absolutely not required, but we are happy to guide you in the contribution process.
|
||||
|
||||
@@ -10,15 +10,17 @@ body:
|
||||
This template helps you propose new features, enhancements, or other ideas for Backstage. You can keep your proposal lightweight, but please provide enough detail for reviewers to understand and respond effectively.
|
||||
|
||||
For complex additions, consider creating a [Backstage Enhancement Proposal](https://github.com/backstage/backstage/blob/master/beps/README.md) (BEP) instead, as this process streamlines discussions and iteration. Don't worry - you can always convert this issue to a BEP later.
|
||||
- type: checkboxes
|
||||
id: issue-labels
|
||||
# This field is managed by .common.yaml
|
||||
- id: issue-labels
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: '📜 Issue Labels'
|
||||
options:
|
||||
- label: 'Please familiarize yourself with the issue labels used in this project: [LABELS.md](https://github.com/backstage/backstage/blob/master/LABELS.md)'
|
||||
required: true
|
||||
- type: textarea
|
||||
id: search-terms
|
||||
# This field is managed by .common.yaml
|
||||
- id: search-terms
|
||||
type: textarea
|
||||
attributes:
|
||||
label: '🔎 Search Terms'
|
||||
render: plain
|
||||
@@ -30,8 +32,9 @@ body:
|
||||
e.g. "catalog github rate limited", "http root service configurer", "scaffolder template include", "entity card title"
|
||||
validations:
|
||||
required: true
|
||||
- type: dropdown
|
||||
id: project-area
|
||||
# This field is managed by .common.yaml
|
||||
- id: project-area
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: '🗃️ Project Area'
|
||||
description: What area of the project would this feature be related to? This will help find an owner for the issue faster.
|
||||
@@ -86,15 +89,17 @@ body:
|
||||
Did you consider any other approaches, and if so, why did you rule them out?
|
||||
|
||||
These do not need to be as detailed as the main proposal, but should include enough information to understand the idea and why it wasn't suitable.
|
||||
- type: checkboxes
|
||||
id: read-code-of-conduct
|
||||
# This field is managed by .common.yaml
|
||||
- id: read-code-of-conduct
|
||||
type: checkboxes
|
||||
attributes:
|
||||
label: 'Have you read the Code of Conduct?'
|
||||
options:
|
||||
- label: 'I have read the [Code of Conduct](https://github.com/backstage/backstage/blob/master/CODE_OF_CONDUCT.md)'
|
||||
required: true
|
||||
- type: dropdown
|
||||
id: willing-to-submit-pr
|
||||
# This field is managed by .common.yaml
|
||||
- id: willing-to-submit-pr
|
||||
type: dropdown
|
||||
attributes:
|
||||
label: Are you willing to submit PR?
|
||||
description: This is absolutely not required, but we are happy to guide you in the contribution process.
|
||||
|
||||
Reference in New Issue
Block a user