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

From: Andrew Ardill <andrew.ardill@gmail.com>
Date: Mar 1, 2012, 12:46 UTC
Message-ID: <CAH5451mx-f0vuJzTRRhs5Ttr6D1HvB6ptoj_=-kyWqkZ=KHJ_Q@mail.gmail.com>
In-Reply-To: <CACBZZX4T28m6k7A53Zc32Aquk-jh7_R0KPeq983bSQ3B-r27cA@mail.gmail.com>

On 1 March 2012 22:54, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 7 quoted lines

> As someone who submits patches every once in a while I can echo other
> sentiments in this thread, just because you have a list of issues that
> doesn't mean anyone is working on them.
>
> However I'd also sometimes like to work on some random issue because
> I'm bored, and having a collection of issues ordered by priority (or
> popularity) would be useful when that happens.

JIRA is particularly good at categorising backlogs and filtering out issues, so this is a very achievable outcome.

> But I think any proposal to set up a wholly external system is going
> to fail, we do most of our bug submission / commenting etc. on this
> mailing list, and that isn't going to change, so there's always going
> to be a large chasm between the list and any external system.

I agree wholeheartedly.

> What I think *would* work however is a system that feeds off the
> mailing list. This could be as simple as a mailing list aggregator
> that allowed you to star certain messages, and the most starred
> messages would be the popular issues.

This is an interesting idea, not sure how that would be implemented though. Seems like you would need some client or webservice email reader that could be extended like that.

Show 21 quoted lines

> A more fancy solution would:
>
>  * Consume every single message that gets sent to the list
>  * Group each thread and allow it to be categorized as a
>   bug/issue/enhancement/complaint
>  * Allow you to mark a collection of threads as describing the same
>   issue, so you'd have duplicates marked & the full history of a
>   discussion on some issue.
>  * Allow you to mark an issue as outstanding / resolved / allow voting
>   on it.
>
> Thus you'd automatically build up an issue database without anyone
> going out of their way, all it would need is the same people who
> complain that they can't file bugs either categorizing existing posts,
> or categorizing a post they just made.
>
> Many bug trackers can be made to work with E-Mail (e.g. Jira, RT
> etc.), although I don't know if they're well set up to follow a
> mailing list like this. I think e.g. Jira assumes that you have a the
> bug id in the subject, and might not be smart enough to group things
> by In-Reply-To headers.

JIRA allows creation of issues by sending emails to a special email address. The process that is used is as follows (take from [1]):

The subject  of an email message is examined for an existing issue key:
 - If an issue key is found in the subject, the content of the email
message's body is processed and added as a comment to the issue with
that issue key.
 - If an issue key is NOT found in the subject, the in-reply-to header
 is examined:
    - If the email message is found to be a reply to another email
message from which an issue was previously created, the body is
processed and added as a comment to that issue.
    - If the email message is NOT found to be a reply, a new issue is created.

As you can see, it _should_ respect in-reply-to headers, however we should probably test this :)

Currently only emails that contain issue keys are being captured, however I will enable issue creation in a throwaway project so we can test them. I might even set up a forwarder to capture all or most of the list traffic to see what happens. If we capture any useful issues in that throwaway project, a valid workflow might be to move them over to the 'real' project to which they belong. Perhaps the volume will be low enough in reality that we can enable issues being created directly in that project, without the move step.

One thing to consider is the notifications sent out by JIRA on different events. We could potentially send an email to the list whenever an issue is commented on, resolved, or something else. The possibilities (and permissions around those possibilities) are quite versatile, and well worth investigating. For now I will try my best to stop _all_ automated responses going to the list, until we can be certain that it won't be just more spam.

Thanks for your thoughts, I think your ideas give a really strong direction for us to investigate further.

Regards,

Andrew Ardill

[1] http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email#CreatingIssuesandCommentsfromEmail-Issuecommentcreation