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

11–20 of 128 posts

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

#11

Post by brayhite »

alangibson wrote: post #5
megous wrote: post #4

No one size fits all and there's no ideal. Choice is necessary. There are some universals though. Fast. I hate waiting 10s for page loads in Jira or anything really, if I'm searching for something. Good data export. Jira is very good with this. You can get XML with all the information, IDs, relationships between things, comments, etc in a single call. With this I can create a tool personalized for my particular use o…

Totally agree on Jira's speed. Watching it creep toward a fully rendered page is what got me thinking about this. I also find customization to be way more trouble than it should be. You basically have to hack it to add a template to the description field.

Our team has been pondering a move from Github’s issue tracking and projects to JIRA, and taking a peak at it has given me similar impressions; incredibly powerful but ultimately too large of an app for its own good. The paid integrations are also a frustrating reality to live with.

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

#13

Post by alangibson »

noir_lord wrote: post #7

Pure API with a trello like level of attention to the API (there API is fabulous). Give devs the primitives to build their own without starting from scratch, my problem (me as sole programmer supporting software that 70 people use) is not the same as yours.

I like the idea of letting people roll their own with a set of primitives, but I'm not convinced that people really want that when it gets down to it. Devs like the freedom to change their tools, but wouldn't most rather be getting real work done than iterating on their issue tracker?

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

#14

Post by iamdeedubs »

alangibson wrote: post #5
megous wrote: post #4

No one size fits all and there's no ideal. Choice is necessary. There are some universals though. Fast. I hate waiting 10s for page loads in Jira or anything really, if I'm searching for something. Good data export. Jira is very good with this. You can get XML with all the information, IDs, relationships between things, comments, etc in a single call. With this I can create a tool personalized for my particular use o…

Totally agree on Jira's speed. Watching it creep toward a fully rendered page is what got me thinking about this. I also find customization to be way more trouble than it should be. You basically have to hack it to add a template to the description field.

Yeah the customization options on JIRA kill me. I have an old joke I always reference when I join a new team

> When your team grows to 25 devs, its an almost certainty that at any point of the day, one of them is adjusting a JIRA workflow

- https://twitter.com/deedubs/status/880819973488340992

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

#15

Post by porphyrogene »

GitHub Issues is nice and simple with sufficient tools to assign and categorize issues. Many similar tools are built on top of GitHub Issues and if they work independently they usually do so with an API that is a carbon copy of GitHub Issues’. If you commit to using GitHub then you can always build your own GUI or let people use Trello on top of it if they choose to do so.

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

#16

Post by alangibson »

whalesalad wrote: post #10

I think it's Trello with an automation and management layer on top. Templates for preconfigured boards, workflows to add custom actions to a list or card, such as 'archive list to xyz board and rename to foo'. Then combine that with some kind of inception where a card itself can be a board that you can "enter". This way when a single card gets too heavy, it becomes a board without all of the ceremony around that.

I love the card-to-board idea. I don't know why more tools don't have a way to 'drill in'. Workflowy is basically built around the idea.

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

#18

Post by alangibson »

brayhite wrote: post #11
alangibson wrote: post #5

Earlier quoted context omitted.

Totally agree on Jira's speed. Watching it creep toward a fully rendered page is what got me thinking about this. I also find customization to be way more trouble than it should be. You basically have to hack it to add a template to the description field.

Our team has been pondering a move from Github’s issue tracking and projects to JIRA, and taking a peak at it has given me similar impressions; incredibly powerful but ultimately too large of an app for its own good. The paid integrations are also a frustrating reality to live with.

It's really capable, but you can feel it getting ready to collapse under its own weight. Same goes for Confluence.

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

#19

Post by bluGill »

Simple to figure out how to fill in all the fields, but not let me get by without adding all the required information.

This does not exist and I've concluded it cannot exist. There is too much information that needed that has to be collected for simple to be possible.

Post reply on HN