Ask HN: What are you using as an issue tracker in 2018?
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.
46 comments
[ 3.4 ms ] story [ 81.1 ms ] threadEdit: 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/
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:
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
One of my main gripes is the ability to atomically update an issue vs incremental updates. For example, Bugzilla allows you to edit multiple fields then hit commit to save, Jira on the other hand applies changes automatically when you edit certain fields (e.g. assignee). This causes people problems (person gets assignment email before the comment about why it was assigned to them has arrived or vice versa), and automation problems (if you have anything driven by receipt of the emails, you now need to collate many before action can be taken). It may well be possible to configure Jira in a way that's more useful to us, but sadly we've got one mega instance that's supposed to be all things to all people and as such, doesn't do many things well!
Used Redmine before Bugzilla and thought that was pretty good.
Yes I can compose my reply in another editor and paste it once it's final. However, IMO an issue tracker is something you use so often that working around these small issues comes at a high cost to me when it should not.
Is this the query language that you are mentioning? I don't have experience with it but from the documentation it looks very limited.
[1]: https://taiga.io/
Redmine Mentions https://www.redmine.org/plugins/redmine-mentions
Redmine Banner https://www.redmine.org/plugins/redmine_banner
Redmine Slack https://www.redmine.org/plugins/redmine-slack
I’m partial to the Agile, Checklists, CMS, and CRM plug-ins from RedmineUp, too. I think they’re essential. There are both free and “pro” versions:
Redmine Agile https://www.redmine.org/plugins/redmine_agile
Redmine Checklists https://www.redmine.org/plugins/redmine_checklists
Redmine CMS https://www.redmine.org/plugins/redmine_cms
Redmine CRM https://www.redmine.org/plugins/redmine_contacts
We still use GitLab, just not for issue tracking anymore. At the free and lower-cost tiers, GitLab lacks a bunch of issue fields (they seem to prescribe using tags for things like priority), and very annoyingly GitLab’s agile board cannot display issue cards from multiple projects simultaneously on one board.
Reasons I like ZenHub:
- everything is just a GitHub issue
- one less login
- GH issues put the content front and center, and let you use markdown. Other issue trackers do a poor job at visually distinguishing the issue metadata and the actuall report.
- Comments are big, first class citizens.
- much lower learning curve compared to Jira, imho.
Ugh, I know all about this. We use Jira where I work and the implementation was so botched and horrible that it easily costs me an hour a day just fighting the awful workflows, required fields, etc., that were put in place by someone who had no idea what they were doing. Not to mention the fact that the same person accidentally wiped out our entire issue database/backlog during a maintenance window one evening.
I’ve worked with Jira before and while it’s not perfect it can be set up pretty well. But, man, when it isn’t, it sure is hell using it.
[1] https://www.tuleap.org/ [2] https://www.tuleap.org/features/issue-tracking
https://clubhouse.io
For small side projects, I tend to just use the repo's issue management. Still looking for a light visual tracker that hits that 'just enough' sweet spot.
JIRA (tasks + bugs) + Confluence (for any kind of internal docs) is all you need.