[Issuetracker-development] Email subject lines, what do you think?
Brought to you by:
peterbe
From: Peter B. <ma...@pe...> - 2004-12-01 13:21:26
|
I'm revamping/restructuring the appears of the email sendouts of the IssueTrackerProduct. A problem that has proven troublesome is that when you add an issue and there's a notification sent out to certain people then the subjectline is generic. This causes problems with threaded email clients like Gmail. The aims of the Always-notify emails subject line: * Generically state the title of the issuetracker from which it is sent * Differentiate between added issues and notification-of-change to existing issues * Contain the title of the issue at hand Suppose the issuetracker instance title is "My Issue Tracker" and the title of issue at hand is "My foo is foobar" (all without the quotes). Here are the alternatives: * My Issue Tracker: new "My foo is foobar" * My Issue Tracker: (new) My foo is foobar * My Issue Tracker: new issue "My foo is foobar" * My Issue Tracker: (new issue) My foo is foobar * My Issue Tracker: issue added - "My foo is foobar" * My Issue Tracker: issue added - My foo is foobar * [My Issue Tracker] new "My foo is foobar" * [My Issue Tracker] (new) My foo is foobar * [My Issue Tracker] new issue "My foo is foobar" * [My Issue Tracker] (new issue) My foo is foobar * [My Issue Tracker] issue added - "My foo is foobar" * [My Issue Tracker] issue added - My foo is foobar I'm personally not very keen on the [angle brackets] because it's a common convention for mailing lists. The quotes are of course excessive but can be very useful to distinctly separate out the issue title. The middle word (new|issue added) can take many different forms but the shorted the better. For notifications of followups I prefer the same subject-line-convention as for new issues but with a different middleword. E.g. (change) or (update). Ideas? Grateful for feedback. Peter -- Peter Bengtsson, www.peterbe.com |