Issue #3299 resolved

Gmail parseable token in email notifications (BB-3142)

bryan hunt
created an issue

When Bitbucket sends out an issue change notification. The email contains the following footer.

{{{ Responsible: userdave --

This is an issue notification from bitbucket.org. Blah blah blah }}}

Anyhow, that isn't very easy to filter when using Gmail, notmuch, etc. It's just not something that's easy to specify using tokens.

It would be awesome - if the email messages contained a parseable token, something like this:

{{{ responsible-userdave -- This is an issue notification from bitbucket.org. Blah blah blah }}}

Just as readable by a developer. But, can be filtered by Gmail. It isn't currently possible to filter by this line, because Gmail, Outlook, etc cant match something that contains a newline character.

Comments (19)

  1. bryan hunt reporter

    We use a single project for all our bugs (some of our developers become easily confused) so filtering by the subject line is insufficient (all the bugs are in our 'planning' project).

    If a bug is assigned to me I want it at the top of my lists.

    I want to filter, by assignee - (potentially) as well as repo.

    I'm actually using notmuch mail as I receive up to 400 messages daily.

  2. Jesper Nøhr

    I understand the need to be able to filter on this, but I'm not a fan of changing the message body to be less readable. Yes, we're (mostly) developers, but it seems this change would make the experience worse, not better.

    I'd prefer something instead, which gives you the same benefit, but doesn't change the message body. Can you set up your client to look at headers? Something like injecting a header a la X-Assigned-To: userdave would be more realistic.

  3. bryan hunt reporter

    Jesper,

    Yes, setting a header would be a more elegant solution. I just picked out the first thing that a quick visual examination revealed.

    There is a larger issue of irrelevant emails being sent to repository subscribers, but adding the header as you describe improve the situation for 99% of user cases.

    Best Regards,

    Bryan Hunt

  4. bryan hunt reporter

    I've just done a bit of research:

    Back to the issue of readability, I really don't think it will make a huge difference, the only change I'm suggesting is to remove a single newline character.

    Current

    Responsible:
    userdave -- 
    

    Proposed

    Responsible:userdave -- 
    

    Alternative proposal

    Responsible userdave -- 
    

    If anything, I'd consider it makes the message, more readable, rather than less readable.

  5. Jesper Nøhr

    I read it, but haven't decided whether we want to do this or not. Again, I see the need, but I'm not entirely sure how to solve it.

    I'll have a look now and will give you an update later.

  6. Jesper Nøhr

    (In retrospect, this was such a simple change, and I'm sorry it took so long to get it through. In my head it seemed like a lot more work, but a quick look at the email template made it clear.)

  7. Log in to comment