# Concerns about feedback and feature request tracking

**URL:** <https://community.fibery.io/t/concerns-about-feedback-and-feature-request-tracking/1555>\
**Category:** Misc\
**Created:** [April 14, 2021, 3:47am UTC](https://community.fibery.io/t/concerns-about-feedback-and-feature-request-tracking/1555 "2021-04-14T03:47:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [April 14, 2021, 2:44pm UTC](https://community.fibery.io/t/concerns-about-feedback-and-feature-request-tracking/1555/4 "2021-04-14T14:44:38Z")

</div>

I very much appreciate the detailed reply, and I largely agree with @Matt_Blais : it seems like you’re doing the best you can with the resources you have. It is good to know that you feel you could be doing better in “bundling” work and distributing effort between big missing features and other things, though. I think that might help address some of the concerns that drove the original discussion, as it does seem like some small, “simple”, and seemingly quick to implement features (like [[PLANNED] Number Field Formatting Options - Currency](https://community.fibery.io/t/planned-number-field-formatting-options-currency/1114)) remain unimplemented for a long time.

Anyway, this is a useful thread to refer back to when frustrations around feature X not being available yet come up. And I don’t know of another company in this product space where I can get such direct, high-level engagement with core team members, and that’s valuable even if my pet features are further down the roadmap than I’d like!

---

_[View the full topic](https://community.fibery.io/t/concerns-about-feedback-and-feature-request-tracking/1555)._
