# Glide sharing known bugs with Gliders

**URL:** <https://community.glideapps.com/t/glide-sharing-known-bugs-with-gliders/22510>\
**Category:** Feature Requests\
**Created:** [February 9, 2021, 11:50pm UTC](https://community.glideapps.com/t/glide-sharing-known-bugs-with-gliders/22510 "2021-02-09T23:50:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [February 9, 2021, 11:50pm UTC](https://community.glideapps.com/t/glide-sharing-known-bugs-with-gliders/22510/1 "2021-02-09T23:50:21Z")

</div>

Resurrecting a just-archived feature request (below) – I don’t think the “Bugs” category is meant for this purpose. I keep a log of all bugs I’ve reported that are yet unresolved, for any number of reasons (with set reminders). Sometimes I follow up a month or two later. Other times I assume nothing will come of it and move on.

Unlike changelogs, bug trackers are typically internal-facing but when a bug has been reported by multiple users, it’s helpful to alert the user base so we can remove the feature from production.

Original request: [Share Known Bugs With Us](https://community.glideapps.com/t/share-known-bugs-with-us/437)

---

<div class="post-metadata">

**Author:** ![Krivo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/krivo/32/5363_2.png) [@Krivo](https://community.glideapps.com/u/Krivo)\
**Post date:** [February 10, 2021, 6:07am UTC](https://community.glideapps.com/t/glide-sharing-known-bugs-with-gliders/22510/2 "2021-02-10T06:07:47Z")

</div>

@Rasha agree with you.