# Issue Tracker for Discourse **URL:** \ **Category:** Development\ **Created:** [June 17, 2024, 10:07am UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354 "2024-06-17T10:07:38Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)\ **Post date:** [June 17, 2024, 10:07am UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/1 "2024-06-17T10:07:38Z")
Continuing the discussion from [Tickets Plugin 🎟](https://meta.discourse.org/t/tickets-plugin/97914/217): I’m looking for a way to either use something like the [Tickets Plugin 🎟](https://meta.discourse.org/t/tickets-plugin/97914), or to integrate with [Forgejo’s issue tracker](https://forgejo.org/docs/latest/user/issue-tracking-basics/) and Discourse. Maybe the latter would be easier to do? * * * When responding to this topic, please consider that the idea is not to make a one-time solution, but to provide an interesting approach for the free software community to integrate with development tools outside Github. [Forgejo](https://forgejo.org/) has precedence as it became the number one choice outside Github and Gitlab, e.g., running at [Codeberg.org](http://Codeberg.org). But one could also consider [SourceHut](https://sr.ht) as it would make a splendid front-end for this minimalist email-based forge for hackers. Originally I intended this topic to be in the #Marketplace, since I wanted someone to pick up the Tickets plugin, but I realize there’s a need for prior discussion before this can happen. Notably, I’d like to know how _you_ are using Discourse in combination of, or as a replacement to, your code forge or project management issue tracker. Discourse team feedback welcome! --- _[View the full topic](https://meta.discourse.org/t/issue-tracker-for-discourse/312354)._