Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What would your ideal issue tracker look like?

news.ycombinator.com

Post reply on HN
Print view View original

91–100 of 128 posts

Re: Ask HN: What would your ideal issue tracker look like?

#91

Post by jasonpeacock »

cryptonector wrote: post #87

I'd like somewhat less emphasis on closing tickets and more on a big picture. Not everything is best represented as a ticket, but JIRA has tended to make management think it can get useful data from it, and that the useful data is "tickets closed" or "time logged". Then employees just optimize for that... Now, one can have tickets open for the purpose only of tracking work towards larger goals -umbrella tickets if yo…

^this. You get what you measure.

To design a better issue tracker, figure out what you need to measure for success and then design a tool to measure that track changes that drive improvements in those metrics.

For example, "feature completeness". When you achieve N of M features complete then you have an Alpha release - now build something to track the progress of those features.

The same for bugs - they're really an aspect of your overall product quality. Figure out what quality metrics are important and build something to track the progress of improving those metrics.

Re: Ask HN: What would your ideal issue tracker look like?

#92

Post by cimmanom »

mcphage wrote: post #36

- it wouldn't assume that problems map 1-to-1 with solutions. A reported problem might require several things to solve, and a solution might handle multiple problems. - it would make it easier to collaborate. Most issue trackers have a single person assigned to a ticket, but I would want multiple: the person working on it, the person testing it. Other people brought in to answer a single question. A person brought in…

We just add fields to the ticket in Jira to track those various responsibilities and use a hook to auto-update them as part of status transitions.

Re: Ask HN: What would your ideal issue tracker look like?

#94

Post by jasonpeacock »

eterm wrote: post #79
geoelectric wrote: post #58

Earlier quoted context omitted.

That's pretty much how JIRA works--based on issue type, you can define "screens" that expose different workflows and data. It's nice if you have a very clear idea of what you want your workflow to be, but can be a bit overwhelming to set up if you don't. Doesn't help they have a lot of different issue types though. It's a kitchen sink implementation for sure.

One trouble with JIRA is that it doesn't come opinionated, this often means that if one team starts tweaking it, another team gets presented with 30 fields and no idea what to do with them all. Or you get one location who try to use it while simulataneously another location might use it in a completely different way, and then it becomes even harder to really keep a grip on what's going on. You also get fights over wh…

This is a JIRA management failure - why is the same workflow being imposed on different teams?

Either the company has agreed that all teams will follow the same workflow, then you do as described above, or each team owns their own workflow definitions.

Re: Ask HN: What would your ideal issue tracker look like?

#95

Post by michaelmure »

DizzyDoo wrote: post #90
michaelmure wrote: post #89

Shameless plug: I'm building an issue tracker integrated in your git repository, decentralized, fully working offline and from your terminal/web browser. If you want to join the fun, feel free :-) https://github.com/MichaelMure/git-bug

I really like the idea of building an issue tracker into the Git file storage! Would you recommend it for use in real life projects yet?

It might still be a little too early, I might still make non-compatible changes in the data model. But that's not too far.

I plan to eventually have the ability to keep reading older version of the data, but it's not there yet.

Re: Ask HN: What would your ideal issue tracker look like?

#96

Post by retzkek »

ludwigvan wrote: post #85

- Editor integration. VS Code integration is easiest nowadays I guess. Most programmers hate leaving their editors and dealing with text entry boxes on browsers. In my projects, we have a wiki and a knowledge_base.md Guess which one I put random tips. - Separating data entry from data organization. This is the fatal mistake every web site does, confusing data entry with organization. Data entry should be free, organi…

> Most programmers hate leaving their editors and dealing with text entry boxes on browsers.

The "Edit with Emacs" extension was a game-changer for me. https://github.com/stsquad/emacs_chrome

Re: Ask HN: What would your ideal issue tracker look like?

#98

Post by edoceo »

We use one system for triage, others for tracking. Support phone, email and social drop in there, mostly closed right away, others then route to the proper system GitHub Issue, Trello, etc. Triage was our biggest pain point. And i wish for a system that forced WIP limits and only one P1

Re: Ask HN: What would your ideal issue tracker look like?

#100

Post by ykevinator »

michaelmure wrote: post #89

Shameless plug: I'm building an issue tracker integrated in your git repository, decentralized, fully working offline and from your terminal/web browser. If you want to join the fun, feel free :-) https://github.com/MichaelMure/git-bug

How are you doing offline on browser?
Post reply on HN