# Public Issue Tracker Board

**URL:** <https://community.iode.tech/t/public-issue-tracker-board/8075>\
**Category:** General Discussion\
**Created:** [21 April 2026 06:16 UTC](https://community.iode.tech/t/public-issue-tracker-board/8075 "2026-04-21T06:16:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![petefoth](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/2acd7d/32.png) [@petefoth](https://community.iode.tech/u/petefoth)\
**Post date:** [21 April 2026 06:16 UTC](https://community.iode.tech/t/public-issue-tracker-board/8075/1 "2026-04-21T06:16:36Z")

</div>

> [@Ota: Missing keyboard on decryption prompt (a5y17lte)](https://community.iode.tech/t/ota-missing-keyboard-on-decryption-prompt-a5y17lte/8066/2):
>
> I need to make sure the team disables their github repos, they have not been used for multiple years.

It would be good to keep using at leat one github repo, one that has an issue tracker. It is a nonsense that iodéOS users have no proper way to raise issues with iodéOS. Using a community forum as an issue tracker is definitely ‘sub-optimal’.

---

<div class="post-metadata">

**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\
**Post date:** [22 April 2026 15:14 UTC](https://community.iode.tech/t/public-issue-tracker-board/8075/2 "2026-04-22T15:14:29Z")

</div>

I do agree a public issue tracker such as nearly all open-source development projects use would be good, especially for developers or more technically-aligned people already on Github / Gitlab. It then allows linking to code bits, referencing commits, PRs from the community, etc.

But, there are some drawbacks as well:

1. Non-technical people will not have an account there. So issues will always be posted here on the forum as well.
2. “False positive issues” will be added to Github (as on the forum), needing triaging, cleanup, and cross-referencing in both places.
3. As Github isn’t the location of the source code, it the technical benefits of having an issue tracker (linking to commits, PRs, etc.) wouldn’t be available.

So all of that indicates that iodé could (should?) consider opening Gitlab registration, but still points 1 and 2 will occur (so only 3 is addressed), and that would then take more admin overhead to manage? Maybe we need to see if we can get some volunteer help to assist?