One significant issue with GitHub issues for ASF projects is that non-committers cannot edit issue or PR metadata (labels, requesting reviews, etc). The lack of formalism around Resolved and Closed states can place an extra communication burden to explain why an issue is closed. Sometimes projects use GitHub labels like 'wontfix'. The issue linking, Fix Version, and assignee features of JIRA are also helpful communication and organization tools.
In other projects I have found JIRA easier to keep a larger number of people, release milestones, and issues organized. I can't imagine changing to GitHub issues in Apache Arrow, for example On Fri, Aug 16, 2019, 1:19 PM Ryan Blue <rb...@netflix.com.invalid> wrote: > I prefer to use github instead of JIRA because it is simpler and has > better search (in my opinion). I'm just one vote, though, so if most people > prefer to move to JIRA I'm open to it. > > What do you think is missing compared to JIRA? > > On Fri, Aug 16, 2019 at 3:09 AM Saisai Shao <sai.sai.s...@gmail.com> > wrote: > >> Hi Team, >> >> Seems Iceberg project uses Github issues instead of JIRA. IMHO JIRA is >> more powerful and easy to manage, most of the Apache projects use JIRA to >> track everything, any plan to move to JIRA or we stick on using Github >> issues? >> >> Thanks >> Saisai >> > > > -- > Ryan Blue > Software Engineer > Netflix >
