Weighing in on Jira specifically - I’ve had to use it on a number of projects, and I’ve never had a good experience with it. That might be because the Jira instances were badly configured - bit if that’s the case, it suggests to me that there’s a deeper problem with Jira being too complex for it’s own good.
On the more broad topic of adopting a new ticket system - historically, I’ve been very much of the same opinion as James. All ticket trackers suck. Trac sucks in ways we understand. However, I think the integration between Trac and Github is sufficiently kludgey that it’s at least worth looking at options. If we’re going to switch (and it’s a *BIG* if), * Open source, and written in Django. * Able to support our workflow, and customisable to adapt to other workflows if we need to * Able to integrate with our authentication mechanisms * Able to deal with our “everyone can contribute” permissions structure (more on this below) * *Completely* seamless integration with the Github PR workflow. On Thu, Jan 7, 2016 at 10:18 PM, Yamila Moreno <yamila...@gmail.com> wrote: > Hi, > > >> Are you already familiar with Trac and the way we use it? >> > > I'm familiar with trac (we were using it some year ago), and I'm a bit > familiar with django workflow because I attended a couple of sprints. > Anyway, I'm not an expert in trac. > > >> >> Key things are: >> >> * integration with GitHub (tickets, login) >> > > Yes, we have. > - Everything is based in a documented API, so with webhooks you can get > new issues in github automatically created in your instance of taiga.io, > as well as comments > - Login with github is a contrib plugin, check it here: > https://github.com/taigaio/taiga-contrib-github-auth > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftaigaio%2Ftaiga-contrib-github-auth&sa=D&sntz=1&usg=AFQjCNEV9cVE4vtaW9WQCLG7cCER1yosmg> > ; there are also other contrib plugins to login with other platforms: > https://github.com/agolden/taiga-contrib-google-auth > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fagolden%2Ftaiga-contrib-google-auth&sa=D&sntz=1&usg=AFQjCNFimBmsrvcBhL-2WtddvnFcGVWJOg> > https://github.com/fedora-infra/taiga-contrib-fas-openid-auth > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ffedora-infra%2Ftaiga-contrib-fas-openid-auth&sa=D&sntz=1&usg=AFQjCNHpzbIvV_C_uNwBoP3UnATmzVFwsw> > > > >> * integration with Django Project login >> > > It's not developed, but it should be easy to create a new contrib plugin > for your instance > > >> * integration with site styling >> > > Yes! > https://taigaio.github.io/taiga-doc/dist/#themes > <https://www.google.com/url?q=https%3A%2F%2Ftaigaio.github.io%2Ftaiga-doc%2Fdist%2F%23themes&sa=D&sntz=1&usg=AFQjCNEUXDsQvw4pvn3OkoUpppV9OgnsZQ> > > >> * workflow >> > > The filosophy behind Taiga is the agile frame (Individuals and > interactions over processes). Thus, workflow is completely free to set; in > a fresh project, administrators can configure the workflow, statuses, name > and colours; which of them are "open statuses" and which one are "closed > statuses". > Related to out workflow is permissions. This is one of the biggest reasons why Github Issues doesn’t work for us. We need to be able to give access to *anyone* to update issues. This doesn’t just mean adding comments - it means progressing a ticket along the workflow, adding flags (or whatever categorisation mechanism exists), even closing issues. Being able to identify members of the core team when they participate in conversations is highly desirable, but not absolutely essential. This is a feature that we’ve added to Trac. Providing the ability for core team members to “lock” certain issues would be a nice-to-have that we don’t currently have. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_eeorkYZmWwm6F4H18pQ7rVy%3D5vAGsv%2BTqv-dK7PFQ%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
