#issue-tracker — Public Fediverse posts

Hmm it’s not easy finding a simple issue tracker that’s cheap or free and that doesn’t use AI.
OpenProject is almost there, but is a bit complicated and does one too many things. I wish there were a self-hosted version like Trello that’s simple to use and install.

#IssueTrackers #IssueTracker

Project #introduction

Introducing DITS — a Developer Issue Tracking System built exclusively for solo developers. 🛠️

Tired of Jira-shaped tools designed for teams of 50? Every feature in those tools assumes collaboration — approvals, assignments, team dashboards — and you pay the complexity tax even when you're the only user. DITS strips all of that away.

What makes it different:

→ Zero-friction capture — create issues from the web app, CLI, IDE, or mobile with minimal keystrokes
→ Keyboard-first design — every action has a shortcut, with a Command Palette (Cmd/Ctrl+K) as the primary interface
→ Sub-100ms interactions — optimized for flow state, not loading spinners
→ Deep Git integration — auto-creates branches from issues, links PRs and commits bidirectionally, closes issues on merge
→ Smart Views — Inbox, Today, Upcoming, and Logbook keep your work organized without manual effort
→ Projects vs. Areas — a first-class distinction between finite work (ship v2.0) and ongoing responsibilities (maintenance, learning)
→ Your data, your rules — full export and portability, always

Tech stack: TypeScript, React, PostgreSQL, Redis, GraphQL (primary) + REST, with native desktop and mobile apps planned.

Currently in early Phase 1 — building out the core foundation. More updates as things take shape.

The project is not #openSource, but in the future, when it's more developed, It probably will be.

#progromming #devtools #issuetracker #buildinpublic #indiedev #typescript #react #solodev

Matt Cengia agreed in 2023: Discord has most of the same problems as Slack, the sole permitted client has flashy distractions, searching history is difficult, and exporting history is infeasible. Describes pros and cons of several alternatives, including Slack, IRC, XMPP, Mattermost, Signal, Discourse, and issue trackers of GitHub and other forges. 3/4
https://blog.mattcen.com/2023/07/04/stop-using-discord-for-your-open-source-communities/

#chat #discord #slack #xmpp #matrix #discourse #IssueTracker #BugTracker #mattermost #signal #github

Dave Cheney went further in 2017: Please stop using chat in general for open-source communities. Even a free protocol like IRC, XMPP, or Matrix disadvantages people with a full-time job and people in less-privileged time zones. Use issue trackers, mailing lists, newsgroups, and other asynchronous forums instead. 2/4
https://dave.cheney.net/2017/04/11/why-slack-is-inappropriate-for-open-source-communications

#chat #timezones #slack #discord #irc #matrix #xmpp #forums #MailingLists #IssueTracker #BugTracker #FreeSoftware #OpenSource #FOSS

Heh, you can add emoji into #GitLab labels.

#inkscape #git #code #IssueTracker

@kaffeeringe

Ich denke, das ließe sich mit (automatisiertem) Tagging und gut benutzbaren Filtern passabel in den Griff kriegen. Und es wäre ja schon auch ein Mehrwert, wenn es eine Anlaufstelle für die von mir wahrgenommenen öffentlichen Probleme gäbe.

Mir geht es auch darum, dass sehr viele Menschen sehr schnell dabei sind, rüde ihren Unmut ins Netz abzusondern, dass aber 0,0 zur Lösung beiträgt, wohl aber die allgemeine Stimmung runterzieht und Zweifel an der Problemlösefähigkeit der Demokratie zu nähren.

Ein Issue-Tracker z.B. mit LLM-basiertem Eingabe-Assistent, könnte, wie gesagt den Unmut aufnehmen und konstruktiv kanalisieren...

Ich versuche den Prototyp demnächst™ mal weiterzubauen. Vielleicht ist ja eine Demo überzeugender als meine lauwarmen Worte 😉

#radar #IssueTracker

@kaffeeringe Ich befürchte, es sind mehr als "zwei oder drei" Hausaufgaben. Und ich befürchte, dass niemand wirklich den Überblick über diese Hausaufgaben hat, weil es nämlich kein schön sauber vorgetragenes Hausaufgabenheft gibt, sondern allenfalls ein paar lose Zettel.

In der Softwarewelt gibt es eine ähnliche Herausforderung ("Überblick über Hausaufgaben behalten"). Dort verwendet man seit Jahrzehnten #IssueTracker um das gemeinsam im Team zu bewältigen.

Ich bin der Meinung, es sollte öffentliche #IssueTracker auch für allgemeine Probleme in der "echten Welt" geben. Dann könnten Menschen ihren Frust in eine detaillierte Problembeschreibung kanalisieren und es würde klar, welche Probleme schon lange bekannt sind, wie der Lösungsstatus ist und woran es hängt.

👉 https://codeberg.org/cknoll/radar

Found the git-bug project today and it seems really cool: https://github.com/MichaelMure/git-bug It stores an issue tracker within the repo itself. It provides cli, tui, and gui interfaces to the tracker data. Anyone used this? #git #issuetracker

Frage an #Abgeordnete + #Stadträte.

Wie organisiert ihr eure Arbeit, damit ihr die Übersicht nicht verliert?

Benutzt jemand einen #Issuetracker, ein #Ticketsystem, #Projektplanungs-Tool um den Fortgang von #Anträgen, Antworten in #Ausschüssen zu verfolgen?

Oder welche Ideen gibt es, wie man #Ratsarbeit in Zukunft rationeller erledigen, um nicht wiederholt gleiche Fragen im Abstand von einem Jahr zu stellen?

Es wechseln ja auch die beteiligten Personen und kennen die Geschichte vom Rat nicht.

Creio que devo reportar a sugestão ao :mastodon: oficialmente. 🤔 Procurar onde. Suponho que no Github. Amanhã. 😴

Se alguém já souber se os desenvolvedores são solícitos... 🙏

Buenas noches 🌛💤

#Mastodon #android #app #IssueTracker

🤔 .o( Wenn Fehler im #IssueTracker 10 Jahre alt werden, muss man dann einen Kuchen buggen? )

#Confidential_issues in the #issueTracker|s of public #Gitea and #Forgejo repositories (https://github.com/go-gitea/gitea/issues/3217) would be very useful (e.g. for user support or for vulnerability disclosures), so I've just added a contribution to the #bounty at https://app.bountysource.com/issues/52815258-confidential-private-issues-on-public-repo

#featureBounty #goLang #VueJS

Happy Birthday #GTFSIssues! Vor 3 Jahren haben wir den #IssueTracker für ÖPNV-Fahrplan-Datensätze gestartet.

Bald 120 Probleme und Änderungswünsche wurden dort bereits gemeldet, knapp 2/3 davon warten allerdings noch auf Behebung/Umsetzung

https://github.com/mfdz/GTFS-Issues/issues #GTFS #OpenData #DataAsAProduct

@ikonoklast @evawolfangel @dukethereal @jedie @jele

Ich vermute, dass ist ein Problem von Medien generell, also nicht nur der deutschen. Das soll aber nicht heißen, dass auch hierzulande nicht vieles besser laufen müsste.

Vielleicht bringt ja die Antwort von @Welchering auf:

https://social.tchncs.de/@cark/107666305691970925

ein bisschen Licht ins Dunkel.

---

Wenn es einen #IssueTracker für gesellschaftliche Probleme geben würde, würde ich zum Thema Quellenangaben in Medien auf jeden Fall eins aufmachen..

We have `!important` label in our internal issue tracker. I really like such small and totally unneeded references. Makes everyday life a bit more interesting IMO:)

#easteregg #issuetracker #random

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten