I don't have a strong preference on prefix vs. suffix.

But I think "[Changed Project Column]" and such is very useful.

It's far better than other apps, where almost every email subject is the same regardless of what happened (to learn anything useful you have to open the email). Gerrit (bug 68598) and Bugzilla are both very bad on this front.

"[Maniphest]" will be useful once we're using other applications, so you can know where it comes from (vs. e.g. Code Review). I have no objection to putting this in the From if that's feasible, though.

I don't see any other way of filtering email other than by subject (for separate tasks from code review, for instance): https://secure.phabricator.com/book/phabricator/article/mail_rules/

Please don't remove (or remove and re-add later, that's just busy work for no gain). Instead do (at most) T947.

For the record (since Lego pointed it out):

"X-Phabricator-Mail-Tags" has some of the needed info, but, from https://secure.phabricator.com/book/phabricator/article/mail_rules/:

X-Phabricator-Mail-Tags: this is attached to some mail and has a list of descriptors about the mail. (This is fairly new and subject to some change.)

(emphasis added)

I have no objection to putting this in the From if that's feasible, though.

Did someone check if this is configurable?

The From field is used to show who performed the action and I'm not aware of configuring that.

Just merged T947: Reduce maniphest prefix/prepend for email subject from [Maniphest] to [M] because the motivation is the same and the discussion is about touching or not the bracketed labels, reducing them a bit or completely, only the application part, or also the actions.

I don't have any strong opinion, but if I would have any, it would be based on the mobile experience. Most tasks should render completely in desktop email clients. So far I haven't got problems in mobile, but I will pay more attention.

It might be helpful to add either the 4-letter Callsigns discussed in T1314 to the email subjects, and/or, to add the Project #tags to the bodies.

Otherwise, there is often no obvious indicator which component an email(/thread) is about, which makes it impossible to create effective mail-filters.

@Quiddity:

It has headers, though:

X-Phabricator-Projects: <#phabricator>

or from another thread I'm on:

X-Phabricator-Projects: <#project-management>, <#triagers>

Sadly, gmail does not let us filter by arbitrary headers,
and phab doesn't have the equivalent of bugzilla's preference for showing them in the body, step #2 here which was its workaround. (That seems to be upstream as https://secure.phabricator.com/T5791 and see also https://secure.phabricator.com/T6297)

(And yes, I feel bad for no longer doing all my email through teletype^Dterminal^Dthunderbird, as I did for the previous 10+ years ;P >.> )

It would be useful to have someone with a vested interest in this feature leading the discussion until reaching an agreement. The implementation of the solution agreed should be trivial, right?

I don't see why a discussion would be needed. The status quo (no brackets) is the consensus and hence policy > must be implemented by default. If someone wants to change the status quo, they are free to look for an agreement.

Did/does anyone else ask for eliminating this? Or only the original task reporter?