Hi Tanya

It doesn't solve my problem either...
Before switching to the cloud, I adjusted subject*.vm files on the server to solve the problem. That was quite simple.

path:
atlassian-jira-software-8.9.0.zip\atlassian-jira-software-8.9.0-standalone\atlassian-jira\WEB-INF\classes\templates\email\subject

files to change:
issuearchived.vm, issueassigned.vm, issueclosed.vm, issuecommented.vm, issuecommentedited.vm, issuecreated.vm, issuedeleted.vm, issuegenericevent.vm, issuemoved.vm, issuenotify.vm, issuereopened.vm, issueresolved.vm, issuerestored.vm, issueupdated.vm, issueworklogdeleted.vm, issueworklogged.vm, issueworklogupdated.vm, issueworkstarted.vm, issueworkstopped.vm

files not changed:
issuementioned.vm

Old original content:
#disable_html_escaping()
($issue.key) $issue.summary

New custom content:
#disable_html_escaping()
$eventTypeName: ($issue.key) $issue.summary

The added “$eventTypeName:” allowed the recipients in Outlook to decide which emails should stay or be moved automatically (to a folder or to the trash).

36002489251d

It does not solve this problem... this ticket is not about varying the email subject for individual conditional notification use cases... here we would want a global setting to change the prefix for all email notifications from the system.

Filtering for only "Jira" is problematic. In fact if you're like our company that uses Google mail, Google ignores the characters "[" and "]" in filters... so for helping to filter emails from the Inbox, a filter for "[Jira]" does not work specifically enough... it will filter any subject with "Jira" in it... which could be about any topic related to Jira, not just notifications. Being able to set something like "Jira CompanyName" as the email notification subject would help to make our email filters more reliable (which is all about efficient productivity... which as I understand it is the fundamental goal of what Jira is for).

Hi all,

There’s now an automation feature that enables you to send email notifications for specific updates in the Jira issue view. This method allows you to configure email notifications based on changes to individual fields, providing greater flexibility and control.

Please take a look and let us know if this solves the problem for you. Your feedback is invaluable and helps us continue improving!

https://confluence.atlassian.com/jirakb/automation-send-email-notifications-for-specific-updates-in-jira-issue-view-1402413202.html

Thanks
Tanya 

Any update on this??

Lets modernise the email. It's a great tool to have so please bring it back up to date!

Ohh. I missed 20th anniversary...
and now unassigned

Is this on the roadmap?

Would love to see this feature added. Hopefully I'm alive to witness it!

Hi, 

I was directed here by Atlassian support.

Our users are asking to have the issue type indicated in the notification subject line. Not having it in prevents them from properly filtering and allocating Jira notification emails.

Just to be clear:

1. They had it in the other system and are surprised and disappointed that such a basic requirement can't be fulfilled.
2. I see this feature request is 19 (nineteen) years old and understand it is perfectly dead. 

Regards,

Inna

Any update on getting the support of this for Jira Cloud? 

Being able to customize the email subject / notification was a key feature and workflow for some our departments, when we was on Jira Server. 

It's currently possible to setup Automations to trigger email with a customized subject using the smart values, we would just like to have it for the default notification emails. 

The format we used in the past; 

[JIRA] (IssueKey) (IssueType) (Status) Subject 

Thanks