feature.yml•1.85 kB
name: Enhancement 🚀
description: Suggest a new feature or other improvement
labels: ["✨ enhancement","needs-discussion"]
body:
- type: markdown
attributes:
value: |
:pray: Thanks for taking the time to fill out this enhancement request! Feel free to ping us on [EventCatalog Discord](https://discord.com/invite/3rjaZMmrAm) if you have any questions or need help.
- type: markdown
attributes:
value: |
## Enhancement Request
- type: textarea
id: use-cases
attributes:
label: Use Case
placeholder: What problem are you trying to solve? Describe a *concrete* example of something you are trying to do and as many details as possible about your motivation, the environment, etc.
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed Solution
description:
placeholder: |
Optionally, describe how you would have ideally wanted EventCatalog to support this use case.
This can be a hypothetical "user story".
The purpose of this section is not to design a complete solution but rather to inspire the designer on what a user would have intuitively expected the solution to look like.
- type: textarea
id: implementation-notes
attributes:
label: Implementation Notes
description:
placeholder: |
Any thoughts regarding how this should be implemented?
- type: textarea
attributes:
label: Community Notes
value: |
<!-- Please keep this note for the community -->
* Please vote by adding a 👍 reaction to the issue to help us prioritize.
* If you are interested to work on this issue, please leave a comment.
* If this issue is labeled **needs-discussion**, it means the spec has not been finalized yet. Please reach out in the [EventCatalog Discord](https://discord.com/invite/3rjaZMmrAm).