Reinstate from name in update notifications

This helps those that have email rules set up.

This is absolutely critical for people to see who is commenting is an actual person! The noreply@my.workfront.com is horrendous and will NOT help in any way in tool engagement, adoption and frankly email best practices. Please return to this to the actual person’s name as the sender.

Agreed.  This critical for our users are really disrupting their workflow.  

Has anyone else been impacted by the recent Workfront email notification changes?

We're receiving a lot of user complaints about these emails:

• When a request is converted to a project, users receive email and in-app notifications for comments that were originally made on the request, even though they're not new comments.
• The new email format no longer includes the previous thread history, making it difficult to understand the context of the latest update.

Are others seeing the same behavior? Is this expected, a known issue, or is there a setting we're missing?

Having the ability to reply to emails allows our low usage users to stay in a platform they are comfortable with (Outlook) rather than having to log into Workfront to reply to a comment. Adobe Support assured us that the new “noreply” address still supports “reply to email”. But seeing a no reply sender suggests that replies are not supported, which can be counterintuitive. We need the user name instead of a “no reply” sender. 

This has caused quite a bit of upset amongst our user base as now has become a lot more difficult to keep an eye on and prioritise updates on busy projects, now all of the comments are getting lost under the same noreply@my.workfront.com sender. Please look into a solution that can re enable the inclusion of the commenter in the sender field.  

It looks like Workfront restored the unique sender names earlier this week (yay), but there is still an issue where emails with the subject line no longer thread like they used to. I dug into this and it appears it is because the emails no longer include the "In-Reply-To" or "References" headers that enable threading. I just put in a support ticket about this, but wanted to share here as well.