Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests

Just a quick status update on where the issue tracker experiment at git-scm.atlassian.net is up to:

The basic structure of the issue tracker is set up, and is ready for people to log bugs if they want to. So far no one seems to inclined, but note that it is still locked down to only people who have both registered, and been promoted to 'trusted'. I will promote everyone who has registered so far to 'trusted' in the hope that some of them might add bugs!

The next main step is to have conversations on the list automatically converted into issues that can be tracked. This will be either by forwarding selected threads to the tracker, or forwarding everything to the tracker and managing it from there. Unfortunately, a recent upgrade broke the (unsupported) ability to create issues from emails[1]. This will hopefully be fixed soon, and when it is we will be able to move this experiment to the next phase.

If anyone has any ideas they would like to test, please let me know!

Regards,

Andrew Ardill

[1] Reply from Atlassian: Officially we do not support (http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand) issue creation from email in OnDemand. The feature request for this functionality is located at: https://studio.atlassian.com/browse/JST-5649

There was the ability to create issues from email if emails were sent to jira@<instance domain> as you tried to setup, but this functionality was not officially supported and broke in the recent JIRA 5 upgrade (which is why you receive those errors).

I believe we are planning to fix this in an upcoming bugfix release within the next several weeks though, so please try again later.