I am -1 on this, but count take it with grain of salt since I am not developing
code. I am generally system agnostic, but the maturity of Jira makes it a far
superior tool for tracking, reporting, and staying organized. I would argue
that since this is an open source project organization is significantly more
important since a lot of disparate users need to be able to understand what is
going on at a high level.
1. Github
* Has very little in the way of organizational options
* Offers issues, labels, a basic Kanban and epics which are immature
2. Jira
* Has very mature set of organization and reporting tools and integrates
with many other platforms
* Offers components, releases, labels, and epics which are all mature
* Offers custom searches which can be shared across the project
* Offers customizable kanbans by release, component, with swimlanes that
can also be customized
* Offers customizable workflow so you can have intake and backlog
statuses added
* Offers customizable report templates
Ryan Durfey M | 303-524-5099
CDN Support (24x7): 866-405-2993 or
cdn_supp...@comcast.com<mailto:cdn_supp...@comcast.com>
From: Dan Kirkwood <dang...@gmail.com>
Reply-To: "dev@trafficcontrol.incubator.apache.org"
<dev@trafficcontrol.incubator.apache.org>
Date: Monday, August 28, 2017 at 10:50 AM
To: "dev@trafficcontrol.incubator.apache.org"
<dev@trafficcontrol.incubator.apache.org>
Subject: Re: [VOTE] Bugtracking in Github Issues
+1
On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri)
<efrie...@cisco.com<mailto:efrie...@cisco.com>> wrote:
We currently use JIRA Issues to track all of the Traffic Control bugs.
Now that we have write access to Github, we can move back to GH Issues for bug
tracking.
This will be a better workflow because its one fewer tool and account to have
to interact with. This will hopefully lower the bar for new contributors to
file bugs and engage with the product. We can also help use it (along with the
milestones) to create more useful changelogs and release notes.
A possible downside is that the Issues are maybe less flexible than JIRA in
terms of permissions, workflow, fields, etc. However, we were using Issues
before we entered the incubator and that was fine for us. Hopefully no one has
developed an attachment for JIRA in the last year.
Please Vote +1 to move to Github Issues or -1 to stay on Jira. I’ll assume a
lazy consensus if there aren’t enough votes.
—Eric
