mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
96 lines
3.1 KiB
YAML
96 lines
3.1 KiB
YAML
name: Bug Report
|
|
about: Create a report to help us improve
|
|
|
|
inputs:
|
|
|
|
- type: description
|
|
attributes:
|
|
value: |
|
|
Verify first that your issue is not already reported on [GitHub](https://github.com/ansible-collections/community.general/labels/bug)
|
|
Also test if the latest release and devel branch are affected too
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: OVERVIEW
|
|
description: 'Explain the problem briefly below'
|
|
required: true
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: SUMMARY
|
|
description: 'Explain the problem briefly below'
|
|
required: true
|
|
|
|
- type: dropdown
|
|
attributes:
|
|
label: ISSUE TYPE
|
|
choices:
|
|
- Bug Report
|
|
required: true
|
|
|
|
- type: textarea
|
|
attributes:
|
|
# For smaller collections we could use a multi-select and hardcode the list
|
|
# May generate this list via GitHub action and walking files under https://github.com/ansible-collections/community.general/tree/main/plugins
|
|
# Select from list, filter as you type (`mysql` would only show the 3 mysql components)
|
|
# OR freeform - doesn't seem to be supported in adaptivecards
|
|
|
|
label: COMPONENT NAME
|
|
description: 'List the component, ie `template`, `mysql_users`'
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: ANSIBLE VERSION
|
|
required: false
|
|
description: |
|
|
If this issue has an example piece of YAML that can help to reproduce this problem, please provide it.
|
|
This can be a piece of YAML from, e.g., an automation, script, scene or configuration.
|
|
value: |
|
|
<!--- Paste verbatim output from "ansible --version" between quotes -->
|
|
```paste below
|
|
|
|
```
|
|
- type: textarea
|
|
attributes:
|
|
label: CONFIGURATION
|
|
required: false
|
|
description: |
|
|
If this issue has an example piece of YAML that can help to reproduce this problem, please provide it.
|
|
This can be a piece of YAML from, e.g., an automation, script, scene or configuration.
|
|
value: |
|
|
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
|
|
```paste below
|
|
|
|
```
|
|
- type: textarea
|
|
attributes:
|
|
label: OS / ENVIRONMENT
|
|
description: 'Provide all relevant information below, e.g. target OS versions, network device firmware, etc'
|
|
required: false
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: STEPS TO REPRO
|
|
description: 'Describe exactly how to reproduce the problem, using a minimal test-case'
|
|
required: false
|
|
value: |
|
|
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
|
|
```paste below
|
|
|
|
```
|
|
- type: textarea
|
|
attributes:
|
|
label: EXPECTED RESULTS
|
|
description: 'Describe what you expected to happen when running the steps above'
|
|
required: false
|
|
|
|
- type: textarea
|
|
attributes:
|
|
label: ACTUAL RESULTS
|
|
description: 'Describe what actually happened. If possible run with extra verbosity (-vvvv)'
|
|
required: false
|
|
value: |
|
|
<!--- Paste verbatim command output between -->
|
|
```paste below
|
|
|
|
```
|