dcb36b27a0
- Removed titles since they don't provide added benefit upon the labels
and would often lead to being submitted with just the placeholder
title.
- Feature request form
- Added further context to benefits field for hopefully better
responses that target the core goal.
- Added a field to ask if feature can already be achieved, to
gain an idea if the submitter has explored other options (if
existing).
- Added a field to ensure the submitter has search the issue list
before submitting.
- Added a field to ask existing BookStack usage time to understand
potential evolution of usage and/or influence of other platforms.
25 lines
749 B
YAML
25 lines
749 B
YAML
name: New API Endpoint or API Ability
|
|
description: Request a new endpoint or API feature be added
|
|
labels: [":nut_and_bolt: API Request"]
|
|
body:
|
|
- type: textarea
|
|
id: feature
|
|
attributes:
|
|
label: API Endpoint or Feature
|
|
description: Clearly describe what you'd like to have added to the API.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: usecase
|
|
attributes:
|
|
label: Use-Case
|
|
description: Explain the use-case that you're working-on that requires the above request.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Add any other context about the feature request here.
|
|
validations:
|
|
required: false
|