Could we please get an update on the progress?

What if I want the receiver to treat a Jira notification as a regular email? One way is to remove the prefix .

Hello David,

Do you know the impact of changing the email prefix?. Did you have any issue regarding to notifications after changing the prefix?. Any other configuration that we should analyze?

Thank you in advance.

Please check the num-lock of your Laptop's keyboard to make this alt+255 work.

Here is my answer on the same question in another place.
https://community.atlassian.com/t5/Jira-Questions/Remove-email-subject-prefix/qaq-p/29383#M434639

In short: use alt-255 space symbol instead of regular "space" (alt-32)
 

any fix for this please?

I believe you can simply satisfy the dumb requirement by holding down the <Alt> key while typing "255" in the prefix field.  It causes a preceding space by it's much more external-customer friendly.

Does Atlassian really care about this ? I don't think there is somebody working on this case.

The "Re:" suggestion was excellent. In MS Outlook that text is removed with the default view and only shows up in the reading pane making it almost as if it doesn't exist.

I've added a new suggestion to change the prefix setting into a Project or Issue type based setting. JRA-63996

Such an easy thing to fix. Shame it has not be prioritised at all. There's really no business or technical reason to force a prefix on all outgoing emails.

Awesome thought Rick! But this is still really dumb. How is it even still open?

I decided to change mine to "RE:" since it is, in fact, regarding the issue referenced. And, most people naturally ignore it.

If it's just an issue with the name "JIRA" itself you can change it to whatever you like, for instance to your company name. Currently you just can't leave it empty which is annoying. I voted for this issue, too, and cleared it on database-level.

As I'm evaluating Jira Service Desk, the [JIRA] prefix will be very confusing to my customers. They are non-technical folks and have likely not heard of Jira and most likely flag it as spam. Therefore, I believe that the email prefix will prevent customers from seeing status of service requests and will hinder the effectiveness of the Service Desk solution. Hence, I've added by vote for this and look forward to a non-database solution.

I agree that this should be fixed an I have voted for this issue. But as a work around that does not include editing the database directly you can type ALT+141 in the prefix field and it puts space that the web configuration will accept.

The fact that the existing code actually checks for a prefix indicates to me this is nothing less than a bug (that would literally take 10 seconds to fix)

Unbelievably disappointing. But since we're not using Jira anymore, oh well.

Hi Martin,
This was added a long time ago, its available in the Diagnostic section of JEMH:

Before submit

After submit

Andy Brook: Do you have a solution in JEMH for this? Can you build one?

Very disapointing, that you don't manage to work on these small and useful improvements of the software.

It seems, as if Atlassian is overextended by managing public issue tracking and keeping track of the wishes and demands of the user community (Otto: "Volklaboration"!) ...

Re: JEMH - for those not able to use script-runner, I've added a form to apply this under JEMH > Diagnostics in v1.7.28+

We have the same problem with this "feature". Using JEMH for sending support status mails - which come with their own subject line. But still JIRA adds its prefix. We added 2 spaces as "prefix" but this looks stupid. This field should be optional.

We too have users not wanting this prefix, I really do not understand why it is made mandatory, especially if you can hack this after the fact. If this workaround applicable to all versions of JIRA and is 100% tested ? - https://confluence.atlassian.com/display/JIRAKB/How+to+remove+the+email+prefix+in+JIRA+SMTP+server+configuration

This is annoying.
We do not want to see that Jira in the Email subject.
This is not needed and just causes 'pollution' in the inbox subjects.

This is an issue for us as well. Can we please get a response from Atlassian on this?

Here's how to work around this...

Using the Script Runner plugin for JIRA, run the following Groovy admin script to punch a null email prefix right into the SMTP Server object...

import com.atlassian.mail.MailFactory
import com.atlassian.mail.server.SMTPMailServer

server = MailFactory.getServerManager().getDefaultSMTPMailServer()
server.setPrefix("")
MailFactory.getServerManager().update(server)

// verify results
MailFactory.getServerManager().getDefaultSMTPMailServer()

heh, hi Matt, hows tricks? I was just alluding to my imminent meal of classes and chips when I'll be cutting up some Atlassian code again - customizations, doable but a pain to manage ongoing. A bit like, oh, JRA-19957 for instance

@andy "Steely knives"? I must be missing something - what is going under the knife?

I agree, its weird that the value is required, especially as there appears to be sufficient checking in the code that actually makes use of the value, see com/atlassian/mail/server/impl/util/MessageCreator.java :

       String fullSubject = subject;
        if (TextUtils.stringSet(prefix))
            fullSubject = prefix + " " + fullSubject;

So why is the UI requiring a value, empty should equal "", which would be handled gracefully (and ignored, as expected) inside the code generating the subject.

Its a trivial thing, but like so many others, unlikely to get attention any time soon. Steely knives at the ready!

This requirement is pretty annoying for us as well and not understandable at all - I'd like to add that the Prefix setting is also inconsistent regarding the related Email from setting, which is located in General Configuration instead; obviously it seems appropriate to locate the future Email prefix setting there as well, besides making it optional in the first place of course.

Thanks!