7e3e8a594f
- Adds issue type to each template - Differentiates user-submitted "Change Request" from internal "Planned Feature". This allows us to separate user-submitted ideas from work we've planned through the new feature workflow, and automatically set the github project. - Adds template for docs change - Makes additional context section optional, I noticed many issues put "n/a" or similar in this section anyway. - Disables blank issue adds generic "Task" issue template
23 lines
625 B
YAML
23 lines
625 B
YAML
name: (Webrecorder Team) Planned Feature
|
|
description: For internal Webrecorder use only.
|
|
title: "[Feature]: "
|
|
labels: ["feature design", "ui/ux", "front end", "back end"]
|
|
type: "Feature"
|
|
projects: ["webrecorder/9"]
|
|
body:
|
|
- type: textarea
|
|
attributes:
|
|
label: Description
|
|
description: A summary of the new or improved feature.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Requirements
|
|
description: A list of software requirements.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Context
|
|
description: Additional context. |