Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-3609

Customize mail subject line

XMLWordPrintable

    • 58
    • 54
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      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 follow the documentation available here for workarounds.

      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

      Original request description

      Currently, it is not possible to customize the subject line for notifications.

      At present it is something like:

      [prefix] action: (project key) summary

      Perhaps a new feature could be to customize what order 'prefix', 'action','project' and 'summary' appear in. This could be done by providing the subject line as a velocity template that we can manually edit.

            [JRASERVER-3609] Customize mail subject line

            Dragan Djurovic added a comment -

            Adding a vote that this would be a great feature to help users manage the flood of emails from Jira!

            Dragan Djurovic added a comment - Adding a vote that this would be a great feature to help users manage the flood of emails from Jira!

            william.taylor added a comment -

            This is very important to me.  I am watching ~ 500 Jira stories from an oversight / compliance point of view.  Jira lets me know whenever ANYTHING in a story changes and there's no way I can tell it that I'm only interested in certain changes, so I can get ~ 200 Jira mails a day and more near deadlines.

            My Outlook screen is so narrow that all I can see of a Jira email is <username> (Jira) and on the next line [Jira - Atlassian Jira] Updates for ...

            I would like the email subject to start with the item key such as RTFH-12443 so I can find all the emails that relate to a given story at once.  Given my volume, I often get 2 or 3 for the same story at once.  Since I can't find which story they relate to without opening them, I just process them top to bottom.  When I've gotten more than one email about the same story, it's pretty common for me to do something that turns out to be nonsensical, embarrassing, or ill-informed because I didn't have the full picture.

            If the subjects started with the Jira key, I could do them together.

            I don't need to know WHO sent the comment until I open the story, so starting with the name of the commenter is no help.  If you just want to put the RTFH-12443 at the beginning of the subject and leave everything else the same, that would be totally fine.

             

            By the way, I see no utility in [Jira - Atlassian Jira] Updates for..  WAY too wordy.  Since there's only one Jira, you could say Jira updates for instead and lose nothing.

             
             
             
             Suggest an answer

            william.taylor added a comment - This is very important to me.  I am watching ~ 500 Jira stories from an oversight / compliance point of view.  Jira lets me know whenever ANYTHING in a story changes and there's no way I can tell it that I'm only interested in certain changes, so I can get ~ 200 Jira mails a day and more near deadlines. My Outlook screen is so narrow that all I can see of a Jira email is <username> (Jira) and on the next line  [Jira - Atlassian Jira] Updates for ... I would like the email subject to start with the item key such as RTFH-12443 so I can find all the emails that relate to a given story at once.  Given my volume, I often get 2 or 3 for the same story at once.  Since I can't find which story they relate to without opening them, I just process them top to bottom.  When I've gotten more than one email about the same story, it's pretty  common for me to do something that turns out to be nonsensical, embarrassing, or ill-informed because I didn't have the full picture. If the subjects started with the Jira key, I could do them together. I don't need to know WHO sent the comment until I open the story, so starting with the name of the commenter is no help.  If you just want to put the RTFH-12443 at the beginning of the subject and leave everything else the same, that would be totally fine.   By the way, I see no utility in [Jira - Atlassian Jira] Updates for..  WAY too wordy.  Since there's only one Jira, you could say Jira updates for instead and lose nothing.        Suggest an answer

            Nick Dring added a comment -

            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.

            Nick Dring added a comment - 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.

            Vishal Gautam added a comment -

            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.

            Vishal Gautam added a comment - 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.

            Vladimir Horev [Raley] added a comment -

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

             

            Vladimir Horev [Raley] added a comment - With our add-on Jirassimo Notifications you can customise email subject using all the fields both, standard and custom, in your Jira issue.  

            José Segura added a comment -

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

            José Segura added a comment - Sorry, but we have updated the system, with the latest versions, and the problem persists

            Evan Goldin added a comment -

            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."

            Evan Goldin added a comment - 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."

            Marc Bauer added a comment -

            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!

            Marc Bauer added a comment - 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!

            José Segura added a comment -


            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

            José Segura added a comment - 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

            Jason Rappoport added a comment -

            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...

            Jason Rappoport added a comment - 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...

              Unassigned Unassigned
              jcmailer Jon Pither
              Votes:
              468 Vote for this issue
              Watchers:
              255 Start watching this issue

                Created:
                Updated: