Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Thomas Kellerer
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 1443075609609-5867093.post@n5.nabble.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Josh Berkus <josh@agliodbs.com>)
Responses Re: No Issue Tracker - Say it Ain't So!  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
>  And email integration for Jira is nonexistant.

That is not true. We do have an email integration where customers can create
issues by sending an email to a specific "Jira Email" address. And as far as
I know this is a standard module from Atlassian. I _think_ it can also be
configured that you can reply to the notification emails and the reply will
be added as a comment to the issue.

> like that you can't have more than one person assigned to a bug

That is true, there is only one "Assignee" for an issue - the person who is
responsible for it. 

But given the flexibility of Jira I'm pretty sure one could configure an
additional field (e.g. "is being worked on by" that can be assigned multiple
users. 

One thing that is indeed still missing is a Git integration the way the
Subversion integration works. Jira scans the commit messages for ticket
numbers and automatically links an issue to the commits. 

Thomas

(Note that I'm not in any way affiliated with Atlassian - just to avoid that
impression)



--
View this message in context: http://postgresql.nabble.com/No-Issue-Tracker-Say-it-Ain-t-So-tp5867020p5867093.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: PATCH: use foreign keys to improve join estimates v1
Next
From: Jeff Janes
Date:
Subject: Re: Spurious standby query cancellations