Redmine

IIRC it's the same with Lotus notes / Domino...

vote for this.
MS Outlook grouping also doesn't work with different subjects.

Just for a reference: #1401 does not work for gmail as of now.

For temporary monkey-patching, so that the mail subject does NOT contain status names, one can modify the 48th and 69th line of "app/models/mailer.rb" as follows:

@@ -48,1 +48,1 @@
-        :subject => "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] (#{issue.status.name}) #{issue.subject}" 
+        :subject => "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] #{issue.subject}" 

@@ -69,1 +69,0 @@
-        s << "(#{issue.status.name}) " if journal.new_value_for('status_id')

I think it would be great if this behaviour can be configured in the application settings, just as different ways of displaying user names (USER_FORMATS in app/models/user.rb).
Hope I could work on this patch when I get time later...

This is very close to #3660. Probably it's better to implement #3660 and fix this in one go.

As for emails grouping in gmail, I found this blog post useful:
http://www.sensefulsolutions.com/2010/08/how-does-email-threading-work-in-gmail.html

I disagree Peter Volkov; this is a longstanding usability issue; and if the fix is simply to remove a field from the email template that should not be blocked on a further enhancement.

If the maintainers agree this is reasonable I'll try to prepare a patch.

Gmail is one of the most used email clients and I think it should be very nice to support email threading. The rule is simple, the subject of the email must be the same.

Go Maeda, do you think that we should do this configurable (ex: Show issue status in email notifications for issues) or we should just remove the status from the subject? IMO, I never found the status information from the subject useful.

Marius BALTEANU wrote:

Go Maeda, do you think that we should do this configurable (ex: Show issue status in email notifications for issues) or we should just remove the status from the subject? IMO, I never found the status information from the subject useful.

I prefer making the subject line configurable rather than simply removing the status. The information that the status has been changed is useful for me.

I will try the patch in #17096#note-19 on my environment and check if the threading issue will be resolved.

Go MAEDA wrote:

I prefer making the subject line configurable rather than simply removing the status. The information that the status has been changed is useful for me.

Thanks, I’ll prepare a patch.

I will try the patch in #17096#note-19 on my environment and check if the threading issue will be resolved.

For Gmail won’t work because the rule for threading uses only the subject, but I’m curios if it’ll fix the problem on Exchange/Office365.

Marius BALTEANU wrote:

For Gmail won’t work because the rule for threading uses only the subject, but I’m curios if it’ll fix the problem on Exchange/Office365.

I have just confirmed that patch #17096#note-19 has no effect on Gmail. Unfortunately, I cannot test Exchange/Office365.

Marius, thank you for the patch. The patch works fine but I have one suggestion.

How about storing the setting value as an Array instead of an integer value, like Setting.notified_events? It is useful when we make the subject line more configurable in the future. For example, we may add a setting to show/hide a project name or tracker name.

Go MAEDA wrote:

How about storing the setting value as an Array instead of an integer value, like Setting.notified_events? It is useful when we make the subject line more configurable in the future. For example, we may add a setting to show/hide a project name or tracker name.

I prefer to do a migration at that moment (it won't be a big deal) because we don't know (or at least me) how this feature will develop in the future. I see at least 3 options :) But if you really want to store it as Array, I can change my patch.

Marius BALTEANU wrote:

I prefer to do a migration at that moment (it won't be a big deal) because we don't know (or at least me) how this feature will develop in the future.

It makes sense.