Suggest an answer

Hi we just moved to Jira cloud and straight away people have noticed in the email subject of notifications we have [JIRA] 

People don't know what it means and don't care. I'd like the option to remove this and add something else.

We do have this need. We just moved our Escalation ticket process to Jira and the biggest complain from many folks is that it is harder to distinguish Escalation mails from other Jira mails. Yes we can use email filter and labels but that requires every user to make changes in their mail client, which is not desirable. We would like emails going out from a particular project to have a different prefix like  [ESCALATION] instead of [JIRA]. If anyone has any workaround solution for this please let me know.

With our add-on Jirassimo Notifications you can customise email subject using all the fields both, standard and custom, in your Jira issue.

Sorry, but we have updated the system, with the latest versions, and the problem persists

Not having this feature (and some changes Atlassian made to the content of the email notification subject line) is causing massive problems at my company. People are constantly missing notifications because they get so many that they don't read all of them. And when the email subject line just says "[JIRA] PROJECT-# SUMMARY", everything is threaded together, whether it's being mentioned in a comment or just a status change to a bug you're watching. This is super frustrating. 

Can this please be fixed? Or at least, can we have a checkbox that says "Email subject simple vs advanced", where simple = today and advanced = actually includes what happened, like "Commented on" or "Edited description."

Also vote for this bug, it's also about including custom fields in e-mail template:

https://jira.atlassian.com/browse/JRA-63561

thank you, guys!

It would be preferable, that there was an option, so that everyone could put the prefix to be better understood. In my case, users see the JIRA as prefix, they understand as a spam and ignore him

I think I have found a solution to customizing the subject line for various projects and adding text, fields, etc...

1. Create different versions of the fields templates (templates/email/html/includes/fields/) - for instance components.vm (stock template), components2.vm (addl templates) etc.
In each instance you can add logic to show various fields - this sample shows components:[Component Names] associated with the issues (note, it is the same as the regular components.vm file but removes the HTML tags...

#disable_html_escaping()
#if ($issue.components && $issue.components.size() >0)
#text("common.concepts.components"):
#foreach ($component in $issue.components)
$component.getString("name")#if ($velocityCount != $issue.components.size()),
#end
#end

#end

2. Change the template for the subject you are looking for. In this example it will change for issues updated:
C:\Program Files\Atlassian\JIRA\atlassian-jira\WEB-INF\classes\templates\email\subject\issueupdated.vm

Here is the script adjustment:

#disable_html_escaping()
#if ($issue.getProject().getString("name") == "Test")
($issue.key) #parse("templates/email/html/includes/fields/components2.vm")
#elseif ($issue.getProject().getString("name") == "Email Test")
[TextHere]($issue.key) #parse("templates/email/html/includes/fields/components2.vm")
#else
($issue.key)
#end

In this sample, it will alter the subject line for 2 specific projects and then make everything else be the standard.

Hope this helps...

The comment in the Description says "Please follow the documentation available here for workarounds.", but none of these workarounds work with JIRA Cloud.

This would be a great feature for us to control the mail flood from Jira!

Hi everyone,

Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.

Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

Hope it on the road map. This would be a very helpful way of receiving e-mails with the ability to sort by subject. I hope we see it soon.

Happy to see this is definitely on the roadmap. I hope the implementation can include what we detailed in AOD-7173 (now closed as a duplicate of this), namely the ability for the subject line to include a short identifier showing what type of change has been made (WorklogAdd, CommentEdit, FileDelete, ScreenshotAdd etc.). This would be a great help when working through a list of email notifications, since the list would be much more informative, and depending on the watcher's role, reading the subject line alone would often be sufficient.

Pre JIRA 5.something the name of the event fired in the post function of a transition used to be included in the email subject. It can still be added but it's a manual change to the velocity template files

Just to provide another use case, I'd like my email subject lines to correlate to my custom transitions in the workflow, as folks have different activities to perform when the issue moves to a new State.

Is there a similar issue logged to add this feature to OnDemand instances?

I'd like to be able to customize the subject line on OnDemand instances of JIRA.

Thank you!

We would like to see this functionality as well. We need to be able to sort based on issue number in the subject line.

Thanks,

Dan

Hi All,

Minyaa 2.2 has been just released with new feature for Timesheet Management with an approbation workflow.
In order to implement a dedicated notification mechanism, 2 new features in Minyaa Core have been introduced, allowing you :

• to define your own Notification Type
• to define your own Mail Template

These solutions requires a small effort in term of development allowing you to integrate your own Notification Types and Mail Templates in a plugin. The definitions will have to be stored as resource and some Classes (1 for Tempate and 2 or more for Notifications).

For the moment, since these extension are embedded in a plugin, there is not yet an editor, but it is more easy to deploy than applying modifications in existing Template.
Next step should a Database Storage, probably an editor and perhaps a dedicated Scheme (To follow ...)

Regards
Vincent
Minyaa Team

Hi Dave,

We have implemented the customization of the mail subject line as a velocity template to keep consistency with the customization of the email body. We have chosen to use Velocity because it gives the power and flexibility for the customization required, and it's a relatively well known templating technology (as opposed to defining our own).

However, I agree with you that this will not give the best ease of use experience especially around upgrading time as the customization won't survive upgrades (without some work). JRA-7266 tracks this aspect especially, so I would refer you to that issue to track the latest on this.

Regards,
Edwin

@Peter -

Can you help me understand why this was implemented via a Velocity template? It would be so much better if
a) it were a text field with keywords and editable via the GUI so that people don't have to go mucking about in their JIRA install and have to learn Velocity.
b) JIRA stored that text field in the database so that it is a setting that survives installs of JIRA version upgrades.

The approach you've taken seems pervasive in JIRA and that causes lots of issues like A and B. I'm trying to sell JIRA internally as "enterprise-ready" but ease-of-use for an IT staff is part of that and JIRA doesn't do well there.

• Dave

We need your implementation to not only allow the exclusion of the key but, when it is exclused, we need the input email parser (or whatever it is called), to search for a key in the body of the emailo if the subject does not contain one. Is this the way it has been implemented? If not, can you advise how we can satisfy the requirement?

Hi Mark,

I can confirm that this scenario will work. The mail handler that processes incoming mail determines the issue id from the subject or the 'In-Reply-To' header of the email. More info can be found here

Cheers,
Peter Leschev [Atlassian]

Hi Edwin,

Thanks for the forecast; that was what I expected.

However, I have a question about how this has been impleemnted.

Our requirement is that all emails about an issue have exactly the same subject. This is because our management use these emails to assess progress etc. and use Outlook. Unlike other mailo clients, Outlook's implmentation of grouping by conversation is actually grouping by subject and does not use the parameter in the header.

Now we know that Jira relies on the issue key being in the subject of the email so it can process emails coming in. It would seem at first glance that thi is no problem because we can ensure that the email subkect is always the same including the key. However, the issue itself is often created by an email which is copied to others and those others want to group the emails from Jira by subject. This means that when we build our velicty template for the Subject it will simplay be the Summary of the issue.

We need your implementation to not only allow the exclusion of the key but, when it is exclused, we need the input email parser (or whatever it is called), to search for a key in the body of the emailo if the subject does not contain one. Is this the way it has been implemented? If not, can you advise how we can satisfy the requirement?

Thanks

Mark

Hi Mark,

Thanks for the interest!

The JIRA team is hard working on a JIRA 4.1 release which we are expecting to be ready in late Q1 or Q2 of 2010.

Cheers,
Edwin [Atlassian]

This is great news. I cannot find anywhere that gives me a date when we can expect Jira 4.1 to be released to customers either Beta of final. Can somebody pleasegive some sort of idea?

Hi there,

I implemented this feature request as my ShipIt 13 project. Subject headings are now configurable via velocity templates (in a similar fashion to how text & html email templates are defined now). This will be available in JIRA 4.1

Cheers,
Peter Leschev [Atlassian]

Another request to the growing list for the ability to customize the e-mail subject...

My client need this functionnality

I think it could be really useful to have a field associated to each project and some keywords to use in this field to compose the mail subject.
The keywords could be (for example):

• issueKey
• issueSummary
• projectKey
• priority
• issueType
• reporter

And then you could customize the project field with something like (other examples):

Field: MyCompany ${issueType} - ${issueSummary}
Result: MyCompany Task - Change the password
MyCompany Bug - The system is down

Field: [${issueKey}] - ${issueSummary} (${priority})
Result: [PRJ-01] - Change the password (normal)
[PRJ-02] - The system is down (blocker)

Field: [reporter] ${issueSummary}
Result: [My client] Change the password (normal)
[Other client] The system is down (blocker)

In my opinion this could be a really good improvement (for this really good product)
Bye
stefano

This is particularly important as the order of the elements is not particularly sensible. It is quite common for people to order their emails by subject and having the action so far to the left of the subject is unhelpful.

I have recently discovered that this "action" as defined by the author of this issue is actually the Event Name triggering the email. Knowing this has helped me workaround my problem bit I still would like to have the power to configure the format of the subjecy line.

Starting with JIRA 3.13 (I think - with customized events) the velocity templates can be modified to alter the issue summary line - not as good as the subject, but sometimes useful.

You can use any of the routines in any of the velocity variables (defined at http://confluence.atlassian.com/display/JIRA/Velocity+Context+for+Email+Templates) to modify the email subject.

You can modify JIRA core source to add additional velocity variables.

Waited a long time for jira..so we kind of implemented it ourselves last year. Our solutions allows an administrator to specify an email prefix (in administration) with keys such as

,

or

. We needed make changes to IssueMailQueyItem, SMTPMailServerImpl,Email, MailingListCompiler etc.

Ex: prefix substituions
[${project.category} Helpdesk] ${project.name} -> [Development Helpdesk] My Propject (where project.category=Development and project.name=My Project)

Since managing custom code changes with jira upgrades is kind of painful, I am hoping Jira would implement something similar in the product so that we do not have to go through this.

You probably need something like this in the send method

 
//EmailSubject emailSubject = new EmailSubject(nontranslatedSubject, getSubjectKey(), getSubjectTrailer(event.getIssue()));
EmailSubject emailSubject = new EmailSubject(nontranslatedSubject, getSubjectKey(), getSubject());

Ok - made an attempt at solving this and have been partially successful.

Modified the java file IssueMailQueueItem but all this did was to change the subject line of emails waiting in the "Mail Queue" as seen under the "Administration" section.

Actual emails received into users' mailboxes had an unchanged subject line.

The edit was as follows:

public String getSubject()
    {
        I18nBean i18n = authenticationConext.getI18nBean();
        EventType eventType = eventTypeManager.getEventType(event.getEventTypeId());
        String emailEventKey = "email." + eventType.getNameKey();
        String i18nValue = i18n.getText(emailEventKey);

        // Check if a translation exists - otherwise just add the event name
        if (emailEventKey.equals(i18nValue))
        {
            //DD090528 //return eventType.getName() + ": " + getSubjectTrailer(event.getIssue());
            return getSubjectTrailer(event.getIssue()) + " : " + eventType.getName();
        }
        else
        {
            //DD090528 //return i18nValue + ": " + getSubjectTrailer(event.getIssue());
            return getSubjectTrailer(event.getIssue()) + " : " + i18nValue;
        }
    }

Next we edited MailingListCompiler. This proved partially successful:

from:

"[JIRA] Commented: (KEY-001) Some Subject"
"[JIRA] Updated: (KEY-001) Some Subject"
to:

"[JIRA] (KEY-001) Some Subject : Commented"
"[JIRA] (KEY-001) Some Subject : Updated"

    private String getTranslatedSubject(I18nHelper i18n, EmailSubject emailSubject)
    {
        String subjectKey = emailSubject.getSubjectKey();
        String translatedSubject = i18n.getText(subjectKey);

        // Return the non-translated name if a translation does not exist
        if (subjectKey.equals(translatedSubject))
        {
            //DD090528 //return emailSubject.getNonTranslatedSubject() + ": " + emailSubject.getSubjectTrailer();
            return emailSubject.getSubjectTrailer() + " : " + emailSubject.getNonTranslatedSubject();
        }
        else
        {
            //DD090528 //return translatedSubject + ": " + emailSubject.getSubjectTrailer();
            return emailSubject.getSubjectTrailer() + " : " + translatedSubject;
        }
    }

This is a bit of a pain as the event comes right at the end and in issues with a long summary it is not displayed in the email client's (Outlook) inbox view.

What we are not sure how to do is to be able to split up the (KEY-001) and the Summary and insert the event between them to give:

"[JIRA] (KEY-001) Updated: Some Subject "

Anyone have any ideas?

Thanks in advance, Dave

Frankly, at a first glance this seems not too hard to provide through templates and it's extremely disappointing.

I'm with the many suggestions for a revised subject line.

For someone monitoring a project, such as I, tracking the series of create - resolved - verified emails is not straight forward since the project code & # are embedded in the subject line following the status.

A more useful format would be:

[jira] (project-#) statusWord: item-Description...

Sorting by subject line would group all email for an issue to aid identification of recent changes and those in need of attention.
It would also simplify management of the email sent from Jira.
I'd feel safe purging a create-fixed-verified series for a given issue.

p.s. I really don't need the '[jira]' prefix when there is the project code.

This is really a needed for us also, we have users who need to classes their email by a 'custom field' type of priority that we made.

This would be a very nice feature and, quite frankly, this is something our current, VERY OLD version of bugzilla (v.2.14) does. Atlassian, why are you not looking into this? This issue has a lot of votes. What else is needed to get the ball rolling on this?

After being frustrated with this, I wrote a script that logs into my e-mail and re-writes the subjects. Now gmail threads reasonably. It's a hack, available at http://github.com/philz/jira-rewrite/tree/master .

One more vote from our side on the same issue:

We too prefer to switch the order of Action and Project Key and add assignee in the subject line of the email, for easy sorting and understanding.

Any suggestions on workarounds are also welcomed, but it would be better if we get the feature implemented in JIRA itself - which has been requested over 4 years.... Make it possible soon.

Just adding our 2c: we have had a number of JIRA users ask for this feature. In particular, they wanted the ability to filter notifications about issues assigned to them versus issues that are not assigned to them...

Hoping Atlassian fixes this. I don't think the suggested workaround (changing JIRA source) is an investment we are willing to undertake.

If this gets implemented, it should be possible to modify the subject line per project.

We have modified the jira source to place the key first. However we just migrated projects from our second jira instance to our first. We now have users complaining that they do not like the order of the subject line with the key first. If this could be specified on a per project basis we could make all of our user happy.

Also the fact that the email prefix is global and not per project is stupid.

We have a Client Support project so all of our emails say "Support" in the prefix, but we also have many other projects that are not support related, but the prefix is set to Support because we want it to say that in emails to our clients. Prefix should also be selectable per project and optional instead of required.

This is up to 160 votes now. How many votes, and comments does it take? There hasn't been a comment from Atlassian since 07'.

Still an amazing product, but it's been over 4 years since this was requested. Please make it happen soon.

The possibility to modify subject would be great. When will it come?

Another vote from me for this issue...

Actually, I could not see why Atlassian is not implementing this feature, as it seems nothing hard to do...

Andreas

Our request is the same as many others have posted to this item:

Simply switch the order of Action and Project Key in the subject line of the email

This facilitates easy sorting by project key in any mail client

All the other email customization requests have merit but this simple and relatively obvious change would make a big usability improvement

Well, I got to experience (in an Atlassian Product no less) how this should work.

I got a request from our Engineering Team to modify how notifications come out of FishEye. I spent about an hour poking around in the template folder for Fisheye getting a handle on how things work. I then spent an hour making the changes.

The result, I have Subject lines which are exactly what I want! Perfect.

It can be done. The question is will Atlassian take the steps to make it happen. Please do. Look at your sister product Fisheye and try it out.

We also made code changes to JIRA and are currently using this order:

• [JIRA] Bug (JRA-3609) Minor Commented: Customize mail subject line

But also for us it is laborious to adapt it for every update. Please take it into consideration for upcoming release(s). THX.

we also would like to have the ticket number first. like (GEN-941) [JIRA] Created: Create Site updates - video.
This enables users to sort by ticket # in their outlook.
can you provide an expected date for this feature or else is there any patch avaialable.

We are looking for this feature. This defect has been open for over 4 years? How many votes does it take to get an enhancement?