2e69d0a425
YAML issue forms with required fields so new reports arrive with the context needed to act on them (version, OS, reproduction steps for bugs; problem-before-solution for features). Auto-applies the matching label. blank_issues_enabled: false forces use of one of the three templates. config.yml also surfaces the Patreon link as a contact option. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
47 lines
1.4 KiB
YAML
47 lines
1.4 KiB
YAML
name: Feature request
|
|
description: Suggest a new feature, command, or improvement.
|
|
title: "[Feature]: "
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the suggestion. Feature requests are easier to act on
|
|
when the **problem** is described first and the **proposed
|
|
solution** second — that way alternative solutions stay on the
|
|
table.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem
|
|
description: What are you trying to do that's currently hard or impossible?
|
|
placeholder: |
|
|
e.g. "When working on long polyline edits I have to type coordinates
|
|
in absolute WCS. AutoCAD's `@dx,dy` relative input would be faster."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed solution
|
|
description: How would you like it to work? Reference existing CAD conventions if relevant (AutoCAD / BricsCAD / DraftSight syntax).
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: Workarounds you've tried, or other designs you weighed.
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Screenshots, mockups, links to related features in other CAD tools.
|
|
validations:
|
|
required: false
|