Live data from Hacker News

Ask HN: What are you using as an issue tracker in 2018?

news.ycombinator.com

1–10 of 47 posts

Ask HN: What are you using as an issue tracker in 2018?

#1
I went through two startups and decided to use Redmine for both. Tried GitHub once and later migrated over, due to data ownership concerns and bad usability for project management. Tried self-hosted GitLab for a small group but abandoned it later due to inconsistency with internal workflow.

Redmine also has its own shortcomings. As a Xoogler occasionally I really miss the ease of use of Google's internal bug tracker.

I've also heard people using Phabricator if they were in FB. But I never had the chance to give it a try.

Re: Ask HN: What are you using as an issue tracker in 2018?

#4
post #3

GitLab is pretty big for a small group. If you thought redmine was ok, try gogs.

It seems that gogs is specifically for Git hosting rather than issue tracking and project management?

its like github-lite, but self hosted. it has an issue tracker. IIRC when I used redmine, gogs issues supports everything in redmine.

Edit: also phabricator is an open source project.. so you dont have to be at fb... I would compare it to github/gitlab: https://www.phacility.com/phabricator/

Re: Ask HN: What are you using as an issue tracker in 2018?

#10
In a true hackerish style, I rolled my own solution: https://github.com/marekjm/issue

Back in 2015, I decided that all the issue tracking systems I knew are too heavy-weight. I don't need kanban, agile, or any other buzz - I just need a simple tool to track my issues. I had several requirements: 1/ it must work off-line, 2/ it must be distrubuted (to allow many people working simultaneously on their off-line clones), 3/ it must work in command line, 4/ it must provide minimum distraction, 5/ it must allow me to tag, and search the issues, and I worked from there.

fast forward to 2018 ...and I'm still using it. It does the job for my Free Software projects, and helps me at work (tested in three companies already). It is definitely not bug-free (but the risk of data-loss should be low), and the installation must be done manually from GitHub, but it Works For Me (tm) ;-)

Sample workflow:

    $ issue open "OH noes, a bug"
    $ issue ls --open
    deadbeef OH noes, a bug
    $ issue slug --git-checkout --git-branch --git deadbeef # or just issue sl -gBC de
    ...hack, hack hack...
    $ git commit -am "Fix"
    $ issue close -g HEAD de
    $ git checkout master
    $ git merge -
By using the `-` as the placeholder for "last active issue" I can make this sequence even shorter. Minimal distraction, no switching between the terminal and the browser, no waiting for slow Web interfaces.

/end of shameless plug

Post reply on HN