RS-1 - Add ticket templates
This commit is contained in:
45
bug_report.yaml
Normal file
45
bug_report.yaml
Normal file
@@ -0,0 +1,45 @@
|
|||||||
|
name: Bug Report
|
||||||
|
about: Report a bug with Ridgway Systems Infrastructure
|
||||||
|
title: "[BUG] "
|
||||||
|
labels:
|
||||||
|
- bug
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the bug.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: steps
|
||||||
|
attributes:
|
||||||
|
label: Steps to Reproduce
|
||||||
|
description: Steps to reproduce the behavior.
|
||||||
|
placeholder: |
|
||||||
|
1. Go to '...'
|
||||||
|
2. Click on '...'
|
||||||
|
3. See error
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: expected
|
||||||
|
attributes:
|
||||||
|
label: Expected Behavior
|
||||||
|
description: What you expected to happen.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: actual
|
||||||
|
attributes:
|
||||||
|
label: Actual Behavior
|
||||||
|
description: What actually happened.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: additional
|
||||||
|
attributes:
|
||||||
|
label: Additional Context
|
||||||
|
description: Any other context, screenshots, or logs.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
30
day_to_day.yaml
Normal file
30
day_to_day.yaml
Normal file
@@ -0,0 +1,30 @@
|
|||||||
|
name: Day-to-Day Task
|
||||||
|
about: A small day-to-day infrastructure task
|
||||||
|
title: "[TASK] "
|
||||||
|
labels:
|
||||||
|
- day-to-day
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the task.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: dropdown
|
||||||
|
id: priority
|
||||||
|
attributes:
|
||||||
|
label: Priority
|
||||||
|
options:
|
||||||
|
- low
|
||||||
|
- medium
|
||||||
|
- high
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: additional
|
||||||
|
attributes:
|
||||||
|
label: Additional Context
|
||||||
|
description: Any other relevant details.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
34
feature_request.yaml
Normal file
34
feature_request.yaml
Normal file
@@ -0,0 +1,34 @@
|
|||||||
|
name: Feature Request
|
||||||
|
about: Suggest a new feature for Ridgway Systems Infrastructure
|
||||||
|
title: "[FEATURE] "
|
||||||
|
labels:
|
||||||
|
- feature
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the feature you'd like.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: problem
|
||||||
|
attributes:
|
||||||
|
label: Problem Statement
|
||||||
|
description: What problem does this feature solve?
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: solution
|
||||||
|
attributes:
|
||||||
|
label: Proposed Solution
|
||||||
|
description: How do you think this should be implemented?
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
- type: textarea
|
||||||
|
id: alternatives
|
||||||
|
attributes:
|
||||||
|
label: Alternatives Considered
|
||||||
|
description: Any alternative solutions you've considered.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
47
infrastructure_request.yaml
Normal file
47
infrastructure_request.yaml
Normal file
@@ -0,0 +1,47 @@
|
|||||||
|
name: Infrastructure Request
|
||||||
|
about: Request a change to Ridgway Systems Infrastructure
|
||||||
|
title: "[INFRA] "
|
||||||
|
labels:
|
||||||
|
- infrastructure
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the infrastructure change needed.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: dropdown
|
||||||
|
id: type
|
||||||
|
attributes:
|
||||||
|
label: Request Type
|
||||||
|
options:
|
||||||
|
- New Service
|
||||||
|
- Service Modification
|
||||||
|
- Service Removal
|
||||||
|
- DNS Change
|
||||||
|
- Firewall Change
|
||||||
|
- Other
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: justification
|
||||||
|
attributes:
|
||||||
|
label: Justification
|
||||||
|
description: Why is this change needed?
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: impact
|
||||||
|
attributes:
|
||||||
|
label: Impact
|
||||||
|
description: What services or users will be affected?
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
- type: textarea
|
||||||
|
id: additional
|
||||||
|
attributes:
|
||||||
|
label: Additional Context
|
||||||
|
description: Any other relevant details.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
58
planned_outage.yaml
Normal file
58
planned_outage.yaml
Normal file
@@ -0,0 +1,58 @@
|
|||||||
|
name: Planned Outage
|
||||||
|
about: Schedule a planned outage for Ridgway Systems Infrastructure
|
||||||
|
title: "[OUTAGE] "
|
||||||
|
labels:
|
||||||
|
- planned-outage
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the planned outage and its purpose.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: input
|
||||||
|
id: start_time
|
||||||
|
attributes:
|
||||||
|
label: Scheduled Start Time
|
||||||
|
description: "Include date, time, and timezone."
|
||||||
|
placeholder: "e.g. 2026-04-15 02:00 UTC"
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: input
|
||||||
|
id: end_time
|
||||||
|
attributes:
|
||||||
|
label: Estimated End Time
|
||||||
|
description: "Include date, time, and timezone."
|
||||||
|
placeholder: "e.g. 2026-04-15 04:00 UTC"
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: affected_services
|
||||||
|
attributes:
|
||||||
|
label: Affected Services
|
||||||
|
description: List all services that will be impacted.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: user_impact
|
||||||
|
attributes:
|
||||||
|
label: User Impact
|
||||||
|
description: How will users be affected during the outage?
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: rollback
|
||||||
|
attributes:
|
||||||
|
label: Rollback Plan
|
||||||
|
description: What is the plan if something goes wrong?
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
- type: checkboxes
|
||||||
|
id: notifications
|
||||||
|
attributes:
|
||||||
|
label: Notification Checklist
|
||||||
|
options:
|
||||||
|
- label: Users have been notified
|
||||||
|
- label: Stakeholders have been notified
|
||||||
|
- label: Monitoring alerts have been silenced
|
||||||
50
security_issue.yaml
Normal file
50
security_issue.yaml
Normal file
@@ -0,0 +1,50 @@
|
|||||||
|
name: Security Issue
|
||||||
|
about: Report a security concern with Ridgway Systems Infrastructure
|
||||||
|
title: "[SECURITY] "
|
||||||
|
labels:
|
||||||
|
- security
|
||||||
|
body:
|
||||||
|
- type: markdown
|
||||||
|
attributes:
|
||||||
|
value: |
|
||||||
|
**⚠️ If this is a critical security vulnerability, please report it
|
||||||
|
privately rather than opening a public issue.**
|
||||||
|
- type: textarea
|
||||||
|
id: description
|
||||||
|
attributes:
|
||||||
|
label: Description
|
||||||
|
description: A clear description of the security concern.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: dropdown
|
||||||
|
id: severity
|
||||||
|
attributes:
|
||||||
|
label: Severity
|
||||||
|
options:
|
||||||
|
- Critical
|
||||||
|
- High
|
||||||
|
- Medium
|
||||||
|
- Low
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: affected
|
||||||
|
attributes:
|
||||||
|
label: Affected Services
|
||||||
|
description: What services or systems are affected?
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
- type: textarea
|
||||||
|
id: steps
|
||||||
|
attributes:
|
||||||
|
label: Steps to Reproduce
|
||||||
|
description: If applicable, steps to reproduce the issue.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
- type: textarea
|
||||||
|
id: mitigation
|
||||||
|
attributes:
|
||||||
|
label: Suggested Mitigation
|
||||||
|
description: Any suggestions for fixing or mitigating the issue.
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
Reference in New Issue
Block a user