mirror of
https://github.com/directus/directus.git
synced 2026-04-25 03:00:53 -04:00
35 lines
2.0 KiB
Markdown
35 lines
2.0 KiB
Markdown
# Request a Feature
|
|
|
|
If you have a great idea for an improvement of the platform, or any other feedback, please make sure to open a new
|
|
Discussion on [our GitHub Discussions board](https://github.com/directus/directus/discussions).
|
|
|
|
## Opening a New Feature Request
|
|
|
|
New feature requests can be opened under the Feature Requests section of
|
|
[GitHub Discussions](https://github.com/directus/directus/discussions). Feature Requests follow a Request-for-Comment
|
|
(RFC) format that allows anybody to fully understand what you're proposing, and help speed up the review and triaging
|
|
process.
|
|
|
|
**While the form might seem intimidating at first, please do fill out all sections with as much detail as possible. The
|
|
less ambiguity around _how_ a feature should work, the easier it is to review, triage, and develop a feature.**
|
|
|
|
## Review Process
|
|
|
|
Once a draft feature request gets 15 or more upvotes, it will be moved to the "Open Feature Requests" category, at which
|
|
point the feature will be considered for inclusion into the project. Once we go over to active development for the
|
|
feature, a new Issue will be created to track the progress of implementation.
|
|
|
|
However, if a feature request doesn't reach at least 15 upvotes within 3 months of it being created, it will be closed
|
|
due to a lack of community interest.
|
|
|
|
## Implementing Accepted Feature Requests
|
|
|
|
It's important to note that Accepted Feature Requests are _not_ an ordered list of things that will be worked on next.
|
|
Even though we strive to prioritize what's being worked on based on community feedback, it's likely that there will be
|
|
times when a feature request is blocked by something else that's prioritized by the team. The implementation of accepted
|
|
feature request is triaged based on a combination of popularity, team availability, timelines, scope of the feature, and
|
|
overall project goals.
|
|
|
|
If you'd like to implement and open a PR for one of the open feature requests yourself, please leave a comment on the
|
|
feature request so we can create an Issue to assign and track accordingly.
|