For whatever it's worth, our company switched from Pivotal Tracker to JIRA because we added a QA team and they wanted all this flexibility in devising bug ticket "workflows." All it did from my perspective is add 47 layers of complexity on top of a massively confusing UI and insists on NOT supporting markdown while using its own sorta-similar-but-different-enough-to-be-constantly-annoying "wiki markup", but it can only be supported in certain fields, only I forget which ones it works in and which ones it doesn't until I've carefully entered all these useful code snippets and links and screenshots and save the ticket and see it's just full of gobbledygook.
TL;DR: HATE IT On Wednesday, January 6, 2016 at 8:34:25 AM UTC-6, Aymeric Augustin wrote: > > FWIW Jira seems to be an exception among bug trackers: some people really > love it, others really hate it. It depends on who set it up and maintained > it in the company where they used it. > > Since we don’t have a resident Jira expert, we run the risk that most of > the Django community will fall into the “hate it” bucket. To me this is one > of the riskier choices we could make. > > Anyway it’s unclear to me that the potential benefits of switching to any > bug tracker could offset the transition costs, as long as Trac is > serviceable. > > We’ll see what happens in 2020 if it doesn’t support Python 3 by then ( > http://trac.edgewall.org/ticket/10083, > http://trac.edgewall.org/ticket/12130). > > -- > Aymeric. > > On 6 janv. 2016, at 15:19, Michael Manfre <mma...@gmail.com <javascript:>> > wrote: > > Agreed with the above for the same reasons. > > On Wed, Jan 6, 2016 at 9:17 AM, Shai Berger <sh...@platonix.com > <javascript:>> wrote: > >> What Marc and James said, and in particular what Daniele said : I get to >> use Jira on a daily basis and find it cumbersome and confusing. >> >> Shai see >> >> >> On 6 בינואר 2016 15:43:02 GMT+02:00, Marc Tamlyn <marc....@gmail.com >> <javascript:>> wrote: >>> >>> Yeah, this is a non-starter for me. All bug trackers are bad, we should >>> stick with the bad one we are used to. >>> >>> Marc >>> >>> On 6 January 2016 at 13:26, Victor Sosa <victo...@gmail.com >>> <javascript:>> wrote: >>> >>>> To answer you question: >>>> There is a plug-in to migrate all the data to Jira and similar to >>>> integrate with any it with any in you infrastructure. (I just don't know >>>> it >>>> all you infrastructure) >>>> >>>> >>>> https://confluence.atlassian.com/jira/importing-data-from-trac-238617182.html >>>> >>>> On Wednesday, January 6, 2016 at 9:15:41 AM UTC-4, Daniele Procida >>>> wrote: >>>>> >>>>> On Wed, Jan 6, 2016, Victor Sosa <victo...@gmail.com> wrote: >>>>> >>>>> >I felt like lost using trac; it is kind of messy. I just don't feel >>>>> >comfortable >>>>> >with it. >>>>> >I see so many open source project using Jira that is just natural. >>>>> Search >>>>> >is easy, categorize is easy, look through the all issues and task is >>>>> quick. >>>>> > >>>>> >I would like to propose a vote on Jira as the bugtracker for this >>>>> project. >>>>> >Just vote + or - to see how many people agree on this. >>>>> >>>>> Hi Victor. It's a reasonable proposition, but it's not simply a case >>>>> of choosing what would be nicer: we also have to make it work in our >>>>> infrastructure - and that's a huge effort. >>>>> >>>>> How, for example, would we migrate the many thousands of tickets from >>>>> Trac to JIRA? >>>>> >>>>> How would JIRA be integrated into our current deployment >>>>> infrastructure? >>>>> >>>>> By all means it's useful to get votes on something like this, even >>>>> before we consider those questions, because if enough people want >>>>> something >>>>> it's always possible - but be aware that simply getting lots of votes for >>>>> it would only ever be the first and easiest step. >>>>> >>>>> Having said that: I prefer Trac to JIRA. It's simpler, and faster. >>>>> >>>>> Daniele >>>>> >>>>> >>>> -- >>>> 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-develop...@googlegroups.com <javascript:>. >>>> To post to this group, send email to django-d...@googlegroups.com >>>> <javascript:>. >>>> 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/3b4a63f0-e3a4-4d9b-837c-ed98d212488d%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/3b4a63f0-e3a4-4d9b-837c-ed98d212488d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> -- >> 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-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> 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/CDE1F163-5500-446F-B8A4-FE512F944C57%40platonix.com >> >> <https://groups.google.com/d/msgid/django-developers/CDE1F163-5500-446F-B8A4-FE512F944C57%40platonix.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > GPG Fingerprint: 74DE D158 BAD0 EDF8 > keybase.io/manfre > > -- > 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-develop...@googlegroups.com <javascript:>. > To post to this group, send email to django-d...@googlegroups.com > <javascript:>. > 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/CAGdCwBtQmB45ogstE2PFE%3DDxw9EVgdjaOyw5UeXKHgLD74dQHw%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-developers/CAGdCwBtQmB45ogstE2PFE%3DDxw9EVgdjaOyw5UeXKHgLD74dQHw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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/9c7a1452-c867-430c-a1f6-9be6f7580daa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
