before we NIH our own software again, i'll do the ritual: —i'm looking for a FOSS issue tracking system that works like a chat/collaborative microblog. —i.e. one should be able to post a new request, which becomes a thread, and this thread can be prioritized and has a status (the thread can be marked as DONE). similar to how code review threads work, but for any issue. —ideally i want the messages to support custom tags to reference/link to items in our (homegrown) ERP system —and good search
i realize this can be done with a kanban / card system. but i don't want the fixed lanes and the dragging stuff around of that. more like a huge linear todo list(s). i want to be able to make my own filters/queries to tune what i need to pay attention to (and others in the team).
also it needs to be built on modern technology, i.e. no old scripting languages like PHP etc.
@mntmn Have you looked at Affine.pro? I guess it won't be what you're looking for, but maybe you can make it work, so I mention it just in case. I have no personal experience with it, I recently came across it as an alternative to Notion. Based on what I see in the templates section, it seems like you can make it into almost anything... https://affine.pro/
we have mattermost but the UI is coded in a way that it's kind of slow and clunky even on fast computers/phones and they will probably never recover from this. also, threads cannot have a status/be completed, or messages sorted by non-time-linear order AFAIK.
@mntmn requesting a compiled language on top of the rest comes off as deeply unserious. What's the actual requirement? Memory constrained environment etc? Why not say that?
@ryanprior why "deeply unserious"? i would understand it if you had asked _why_ i have this requirement instead of just trying to judge me like that without knowing the background?
i've been writing web-based software for more than 20 years professionally on all kinds of stacks like perl (starting with cgi-bin), php, java, scala, ruby (merb, rails, sinatra), python (bottle, django), go and rust. that's why i have experience and preferences for what i would like to maintain/host.
@mntmn saying "I prefer a compiled binary for deployment simplicity" makes sense. Framing that requirement as "needs to use modern technology" came off as whimsical 🍃