What's Next

Don't display new feature submissions until a maintainer has reviewed them.

Allow approved members to bypass moderation inbox.

Tools for assessing quality of feature submission and asking the original user for more information to improve the submission.

Add a URL to each feature which could provide more context

Add a filter to the features list to allow users to show only their own suggestions to track their status

Ability to indicate that one feature is dependent on another being completed first.

Allow cross-linking dependent tasks using markdown [link syntax] - description editor should detect the user inserting a link and offer matching features from the same project by title for completion.

Adding a link should automatically add that feature as a dependency, but the user should be able to quickly remove dependencies before submission. Maintainers should also be able to edit the dependencies as needed.

While adding this functionality, comments should also provide the same assistance for linking to features.

Ability to flag features and comments as inappropriate as a non-admin user

Export the current feature list to a CSV or Excel sheet using the selected filters.

Capture date of completion and show on cards

Allow AI agents to collaborate on feature discussions (update implementation plan in response to comments, pick up tasks marked as ready for development, etc)

An image to illustrate the project or feature

Current project descriptions are useful for roadmap/feature page to introduce the project, but too long for a project listing.

Add an additional 'tagline' or 'summary' field which will be displayed below the title in search listings. If not specified, take the first line of the description as plaintext.

Allow extra tags to be added to features to track release versions or other metadata beyond main category

The ability to respond to another user's comment with a 'thumbs up', for example.

Allow users to support a feature they need with financial backing.

• contingent on completion of the feature?
• would overall project sponsorship and sponsor badges be more suitable?

• Split a feature
• Mark as a duplicate

Create Trello cards when new features are submitted, or create and update features when Trello cards are updated.

Integrate with GitHub issues:

New Github issues should create a corresponding feature entry, and new feature requests without an issue should create one (after [Moderation Inbox] accepts the feature?). Maintain the link between the two and mark features as completed/rejected when the issue changes.

Support block quote and code syntax:

> block quote

`` code block ``

Editor should detect if you are pasting into a block quote and prefix each paragraph with the > character.

Similar to support tickets or JIRA issues, give each feature a short ID that can be used to refer to it in descriptions or comments, interacting with the [Feature Dependencies]

The icon at the top-right of a card could be a '+' for example, for quick feature adding to a project. I'm thinking of decreasing no. of clicks when you have a few projects on the go.

The ability to add a category when in triage view?

Allow managers to toggle a mode where they can view the project as a member would see it.

Currently the feature and product searches are implemented as a filter on the full list of records.

Add an extra full-text index for more efficient queries when there are large numbers of features and projects.