Accelerating development - how can we make obsidian feature requests more actionable?

Use case or problem

As an enthusiastic Obsidian user, I’ve noticed that many valuable feature requests remain unimplemented for long periods. While I understand and respect that Obsidian maintains a careful, quality-focused development pace, I’m wondering if there are ways we as a community can better support the development process within the existing framework.

Proposed solution

I’d love to understand if there are ways users can make feature requests and feedback more actionable and useful for the development team. For example:

  • Are there specific types of information that would make feature requests easier to evaluate?
  • Would more detailed use cases or workflow examples help?
  • Is there anything the community could do to make testing or feedback more efficient?

Current workaround

Currently, users wait for features to be implemented or seek plugin solutions where possible.

1 Like

Love the enthusiasm in this community. It’s infectious.