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

121–128 of 128 posts

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

#121

Post by myownlittlworld »

liveoneggs wrote: post #29
alangibson wrote: post #21

Earlier quoted context omitted.

> entire issue tracker hosted/versioned in git I've been mulling over something like that. I don't see why issue tracker, documentation store (wiki, etc), and source code repo need to be separate. Seems more like path dependency more than reasoned choice.

https://www.fossil-scm.org/index.html/doc/trunk/www/index.wi...

I wish there was some way to modify fossil data from within the repository itself. Like, if fossil's bug list were duplicated as files in the issues/ folder, and I could edit the bugs individually as files.

Yeah, if there were some way to combine fossil and org-mode, that would be perfect. As it is, fossil by itself comes pretty darn close for me.

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

#122

Post by Karunamon »

alangibson wrote: post #44
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…

> Most issue trackers have a single person assigned to a ticket, but I would want multiple Totally agree here. Having a single assignee is total nonsense. Makes you wonder if the people building the tool use it. > rigid set of states and transitions I think the whole idea of a set workflow is a relic from the 90's that has little basis in reality, especially in an agile development team.

I have to disagree with multiple assignees here for two reasons:

- Accountability. If it’s everyone’s job, it’s nobody’s job. This is project management 101, every task needs a single person who is responsible for ensuring that task is done.

- Scope. If you feel like you need multiple assignees, this can be a signal that your task is too high-level and needs broken down into smaller units of work (which will generally have one assigned). Something like Jira offers epics, stories, and any other custom issue type you can imagine for doing this.

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

#123

Post by mcphage »

Karunamon wrote: post #122
alangibson wrote: post #44

Earlier quoted context omitted.

> Most issue trackers have a single person assigned to a ticket, but I would want multiple Totally agree here. Having a single assignee is total nonsense. Makes you wonder if the people building the tool use it. > rigid set of states and transitions I think the whole idea of a set workflow is a relic from the 90's that has little basis in reality, especially in an agile development team.

I have to disagree with multiple assignees here for two reasons: - Accountability. If it’s everyone’s job, it’s nobody’s job. This is project management 101, every task needs a single person who is responsible for ensuring that task is done. - Scope. If you feel like you need multiple assignees, this can be a signal that your task is too high-level and needs broken down into smaller units of work (which will generall…

> every task needs a single person who is responsible for ensuring that task is done.

Indeed. But "done" means different things to different people—to the developer, to QA, to deploy engineers, to devops, to the stakeholder. And more goes into a ticket than done/not done, that needs other people to chime in.

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

#124

Post by TXV »

I'm using Nulab's Backlog. This is sort of a shameless plug since I work for that company. However I must say that after several years of clunky issue trackers, this one feels very very refreshing. I won't waste your time with marketing speech, which you can find plenty of on the official website. But actually easiness of use and moderate configurability, plus a decent-looking UI, are the points our advocates praise most often.

The company is very strong in Japan, where it was founded, but rather low-key in the rest of the world. I never heard of it myself before I joined, but after starting to actually use the product, I really wish I had.

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

#125

Post by dsumenkovic »

laurynas-s wrote: post #105

Moved away from Jira to GitLab and it is almost perfect. Some features are missing, but I hope the GitLab team will add sooner or later. In Jira, there was too much customisation which made it difficult to configure properly and as many times I tried to come up with perfect workflow, I have failed to do.

Hey laurynas, we'd love to hear what features you are missing. Is there already a feature proposal? If not, feel free to raise one over at https://gitlab.com/gitlab-org/gitlab-ce/issues.

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

#126

Post by jesterson »

TXV wrote: post #124

I'm using Nulab's Backlog. This is sort of a shameless plug since I work for that company. However I must say that after several years of clunky issue trackers, this one feels very very refreshing. I won't waste your time with marketing speech, which you can find plenty of on the official website. But actually easiness of use and moderate configurability, plus a decent-looking UI, are the points our advocates praise…

I switched to Backlog too. Despite it being rigid (wee, being japanese product says for itself) and having small issues here and there, I can't complain much.

Most important points for me with backlog are:

- impossible to define task/issue additional states. - email notifications are not working sometimes

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

#127

Post by SamWhited »

nurettin wrote: post #64
SamWhited wrote: post #62

I basically want something that's not associated with any service (eg. I shouldn't have to create a Git repo on GitHub just to use their simple issue tracker), is easy to use for non-devs, and doesn't have any complexity: I want a form (possibly with some templates) where I can type text, the ability to comment, and maybe labels for organization and search. I've actually been working on something like that, but it's…

you mean like taskwarrior?

I also want it synced across all of my machines, so probably with some sort of cloud service, and want to be able to share it with other people (so as much as I like a good TUI, I probably can't convince my coworkers in marketing or sales to use it); but that does look really nice still.

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

#128

Post by nurettin »

SamWhited wrote: post #127
nurettin wrote: post #64

Earlier quoted context omitted.

you mean like taskwarrior?

I also want it synced across all of my machines, so probably with some sort of cloud service, and want to be able to share it with other people (so as much as I like a good TUI, I probably can't convince my coworkers in marketing or sales to use it); but that does look really nice still.

I use it with a self-hosted nextcloud. Integrated with jira so I can open issues really fast (thanks to pro: flag) boss is happy and collegues have no idea how I use jira so efficiently.
Post reply on HN