Re: No Issue Tracker - Say it Ain't So!

From: Torsten Zuehlsdorff <mailinglists(at)toco-domains(dot)de>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: No Issue Tracker - Say it Ain't So!
Date: 2015-09-24 07:42:58
Message-ID: 5603A982.5050209@toco-domains.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 24.09.2015 01:33, Josh Berkus wrote:
> On 09/23/2015 03:05 PM, Jim Nasby wrote:
>> On 9/23/15 3:12 PM, Thomas Kellerer wrote:
>>> They also support Postgres as their backend (and you do find hints
>>> here and
>>> there
>>> that it is the recommended open source DBMS for them - but they don't
>>> explicitly state it like that). We are using Jira at the company I
>>> work for
>>> and
>>> all Jira installations run on Postgres there.
>>
>> I'll second Jira as well. It's the only issue tracker I've seen that you
>> can actually use for multiple different things without it becoming a
>> mess. IE: it could track Postgres bugs, infrastructure issues, and the
>> TODO list if we wanted, allow issues to reference each other
>> intelligently, yet still keep them as 3 separate bodies.
>
> Speaking as someone who uses Jira for commericial work, I'm -1 on them.

Full ACK. -1 from me too.

Greetings,
Torsten

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Torsten Zuehlsdorff 2015-09-24 07:43:56 Re: No Issue Tracker - Say it Ain't So!
Previous Message Jeevan Chalke 2015-09-24 07:36:22 Re: TEXT vs VARCHAR join qual push down diffrence, bug or expected?