Page MenuHomePhabricator

Reduce maniphest prefix/prepend for email subject from [Maniphest] to [M]
Closed, DuplicatePublic

Description

Several people have said they like the prepend per app (mostly people who have tested having both Maniphest and Differential in labs). Several people have said they are annoyed by the use of space in every title. Indeed, it really becomes useful as the apps installed span further. But either way for now I vote we reduce the identifier to [M].

metamta.maniphest.subject-prefix

Event Timeline

chasemp raised the priority of this task from to Needs Triage.
chasemp triaged this task as Medium priority.
chasemp updated the task description. (Show Details)
chasemp changed Security from none to None.
chasemp added a project: Phabricator.
chasemp added a subscriber: Eloquence.
chasemp added a subscriber: chasemp.
Aklapper renamed this task from reduce maniphest prepend for email from [Maniphest] to [M] to Reduce maniphest prefix/prepend for email subject from [Maniphest] to [M].Oct 28 2014, 4:54 PM
Aklapper added a subscriber: Nemo_bis.
Aklapper added a subscriber: Aklapper.

For the records, a proposal to mostly get rid of them is T650.

This comment was removed by Qgil.

This is going to break people's mail filters :/

But really, I find the "action taken" (Commented On, Changed CC, etc) part the most annoying.

[Maniphest] [Commented On] T839: Bump minimum PHP version for MediaWiki to 5.3.3 (3 messages)

[Maniphest] is just like any mailman list or [Gerrit]. Shortening it to [M] is kind of pointless, at that point you might as well get rid of it (don't!) since T### already indicates Maniphest.

I personally don't see the need of shortening. (iow: +1'ing Lego.) Also, since there are no easy X-headers to filter on based on which application sent the mail (see: https://secure.phabricator.com/book/phabricator/article/mail_rules/) making things explicit in subject is good, imo.

If [M] conveys as much meaning as [Maniphest] and allows better readability (on mobile platforms especially) it seems like a reasonable compromise between nothing and something?

In T947#16183, @chasemp wrote:

If [M] conveys as much meaning as [Maniphest] and allows better readability (on mobile platforms especially) it seems like a reasonable compromise between nothing and something?

If you insist :) My phone (Android) with the Gmail app (since it's my work account) already auto-shortens things in brackets at the beginning of a subject, eg: this bug appears as (in portrait mode):

[Maniph...] [Commented On] T947:
Reduce mainphest prefix/prepend for...

(it doesn't show a first line of the email body)

In landscape mode it displays the full subject (all of it, including the first 7 or so words of the body).

K9 doesn't do any shortening, fwiw.

For explicitness's sake: [M] is probably fine, but I'm also fine with [Maniphest]. /me unsubs

Qgil lowered the priority of this task from Medium to Low.Nov 7 2014, 9:56 AM
In T947#16170, @Legoktm wrote:

This is going to break people's mail filters :/

But really, I find the "action taken" (Commented On, Changed CC, etc) part the most annoying.

I find this useful. If the CC, priority, or swim lane of a bug I'm just watching changed, I may not even need to open the email. If someone commented, I'm probably going to want to look at that.

I realize this is configurable (e.g. you can disable email for "A task is moved between columns on a workboard."). But that's very coarse (no swim lane emails for any bugs or swim lane emails for all bugs). In reality, you may only care about certain changes for certain bugs (e.g. I'm more likely to care about a swim lane change for a Flow/Echo bug).

I'm fine with shortening it to [M] (though this will break down for Differential/Diffusion), but I have no problem with [Maniphest].

I find this useful. If the CC, priority, or swim lane of a bug I'm just watching changed, I may not even need to open the email

Then your email settings are wrong, change them so that you don't receive emails for those actions. Notification settings are where to control and customise how you (re)act to specific actions, not email subjects.

I find this useful. If the CC, priority, or swim lane of a bug I'm just watching changed, I may not even need to open the email

Then your email settings are wrong, change them so that you don't receive emails for those actions. Notification settings are where to control and customise how you (re)act to specific actions, not email subjects.

Note the second paragraph of the comment you replied to. There is no way to say e.g. "I am interested in swim lanes changes in Core Features projects, but not swim lane changes in Ops or Phabricator projects".