Hello,
I would like to know how to update Email Prefix in the Outgoing email base on the JIRA Project name.
Is it possible?
Thank in advance.
Hello @Great
Thank you for reaching out.
Per your description, I understand you are trying to dynamically change the prefix of your outgoing e-mail address depending on the project related to the notification. Is that correct?
Unfortunately, Jira does not a feature to do that, however, we completely understand how useful this option would be. That being said, we created the following feature request to implement this option:
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
For possible workarounds, you can check the following documentation:
Let us know if you have any questions.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.