# Issue Tracker for Discourse
**URL:** https://meta.discourse.org/t/issue-tracker-for-discourse/312354
**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:** 14
**Page:** 1
### Author:  [@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!
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [June 17, 2024, 11:09am UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/2 "2024-06-17T11:09:11Z")
> [@hellekin](#):
>
> 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.
Another approach would be to develop a system that uses the [Assign Plugin](https://meta.discourse.org/t/discourse-assign-plugin/58044). I think that could meet most of the criteria of an issue tracker or ticketing system.
> [@hellekin](#):
>
> Discourse team feedback welcome!
Probably no one knows more about it than they do.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 17, 2024, 4:44pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/3 "2024-06-17T16:44:51Z")
Yes, extending or using the Assign plugin could be useful. Since @angus is busy elsewhere, I also wanted to test the water and see if there’s somebody interested in doing such work. With the still ongoing NGI Zero grants, this could be funded work.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [June 17, 2024, 5:26pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/4 "2024-06-17T17:26:06Z")
Pavilion can take on new projects.
We just need the following:
- a functional spec
- funding
- a contract
🙂
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 17, 2024, 5:27pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/5 "2024-06-17T17:27:59Z")
Do you think it would be better to build on Tickets, on Assign, or do something else?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [June 17, 2024, 5:28pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/6 "2024-06-17T17:28:25Z")
Do we have a functional spec?
If not, let’s have that first!
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 17, 2024, 5:48pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/7 "2024-06-17T17:48:17Z")
I have posted a similar [proposal to Forgejo](https://codeberg.org/forgejo/discussions/issues/81#issuecomment-2029221) since they have a discussion about using the issue tracker as a discussion space. I think a Discourse integration would bring the best of both worlds.
From the top of my head, a functional spec would be:
- support multiple repositories
- (maybe multiple organizations)
- automatically create topics when issues are created
- (maybe limited to issues tagged as discussion)
- automatically create an issue when a tagged topic is created
- (maybe as a ticket)
- integrate remote users either through SSO (e.g., Oauth2) or ActivityPub (if ActivityPub plugin is present)
- Provide a simple dashboard on the discourse
- with filtering capabilities
- maybe with kanban support
Of course this would require a bit more discussion and refinement before we can conclude on a suitable project.
---
### Author:  [@blaisep](https://meta.discourse.org/u/blaisep)
#### Post date: [November 6, 2024, 5:29pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/8 "2024-11-06T17:29:21Z")
Oh! I just posted [Using discourse to track issues?](https://meta.discourse.org/t/using-discourse-to-track-issues/334811)
because I thought that this was already a thing.
I would be willing to use my Discourse instance to prototype any ideas or suggestions
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [November 6, 2024, 5:34pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/9 "2024-11-06T17:34:09Z")
if you have budget, consider posting in #Marketplace.
---
### Author:  [@blaisep](https://meta.discourse.org/u/blaisep)
#### Post date: [November 6, 2024, 5:46pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/10 "2024-11-06T17:46:15Z")
Thank you, good suggestion.
Since the project has long lived issues with long running discussion threads, I think I will create some categories and topics in my Discourse server and give us a chance to work through a few cycles so we can identify requirements.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [November 6, 2024, 5:46pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/11 "2024-11-06T17:46:44Z")
Sounds like a good approach 👍
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [August 21, 2025, 10:46am UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/12 "2025-08-21T10:46:27Z")
Any progress on this?
The tickets plugin seems to have stalled and present some small bugs that are unlikely to get fixed without more precise intervention. Yet, I’m more interested in using web hooks and integrating with Forgejo, since this is what it’s made for and supports code integration. But both the Discourse and the Forgejo community seem to have ignored the proposal. 🤷
@blaisep did you find a suitable solution for your case?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 21, 2025, 10:52am UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/13 "2025-08-21T10:52:36Z")
I built
> [@Process Manager left\_right\_arrow - formerly "Discourse Workflow"](https://meta.discourse.org/t/discourse-workflow/347110):
>
> information_sourceSummary A process management plugin for Discourse that moves work through configurable steps with actions, list filters, charts, swim-lane views, and Kanban boards.hammer_and_wrench[Repository Link](https://github.com/merefield/discourse-process-manager)[https://github.com/merefield/discourse-process-manager](https://github.com/merefield/discourse-process-manager)open_bookInstall Guide [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157) Enjoying this plugin? Please star it on [GitHub](https://github.com/merefield/discourse-workflow)! pray
which allows for complex human workflows and burn down stats.
---
### Author:  [@blaisep](https://meta.discourse.org/u/blaisep)
#### Post date: [November 10, 2025, 10:17pm UTC](https://meta.discourse.org/t/issue-tracker-for-discourse/312354/14 "2025-11-10T22:17:25Z")
We ran into a number of OSI layer 9 (politics) conflicts, so we made no progress. That said, I’m going to look at the links from @merefield ( 🙇♂️ )with great interest because so far it looks like he really gets it.
In other news, the #fedora community is deprecating their forge and looking into portable ways of incorporating workflow into the git host of choice (forgejo, codeberg, etc). There is a lot of interest in reducing the dependency on [github.com](http://github.com) for, reasons.