@Mention Notification Templates

JIRA Cloud - how do we update the template for @mentions emails?





1 answer

0 votes

Hi Matt,

Currently this is not possible per the Restricted functions in JIRA Cloud applications knowledge base article:

  • Restricted function: Customize Jira notifications
  • Configurable on request? No

To customize Jira notifications, one must edit Velocity files within the Jira web app.

This makes it a special case of "customizing source files". See the Suggestion at CLOUD-1791 - Customize notification email template Closed and the Suggestion at JRASERVER-7266 - Create an Email Template Editor in the UI to Replace Editing Velocity Templates.

At this time CLOUD-1791 is closed but you can still vote on JRASERVER-7266 and add your comments for the developers.



That's quite disappointing as the notification doesn't show the organisation or customer name so our engineers that are mentioned do not know who it is in reference to.



Hi Matt,

I definitely understand.  Please vote on JRASERVER-7266 so we can get this added to JIRA.



That doesn't help as that is for JIRA Server whereas the corresponding Cloud ticket (marked as resolved) states;


"In the spirit of transparency, we are going to close this feature request for JIRA Cloud. It's been 18 months since we last provided an update and we do not have any plans to introduce support for custom email templates in JIRA Core or JIRA Software. (This is how we've been interpreting this feature request, as editing velocity templates has never been possible for JIRA Cloud). If you are a JIRA Server customer, please continue watching JRASERVER-7266 for updates."


Which, to me is a lazy and not a customer-focused response - we're closing the ticket because we haven't bothered to update it in 18 months, we've been interpreting the ticket how we please and haven't requested clarification from users and because this has never been a feature of JIRA previously, we aren't adding it.

@Branden McElveen


Assume this is another ticket that'll be ignored until it is closed with no appropriate answer and no further action?

The fact it hasn't been closed recently means that assumption is incorrect.  Atlassian started an initiative to review all open requests in their Jira a few months ago, and this one survived the initial run of "close if we're sure we won't do it"

@Nic Brough [Adaptavist]


An update or response to the ticket would prevent such assumptions.

The comment on it already states the current standing, that's not changed.  But it has not been closed.

@Nic Brough [Adaptavist]


The comment told me to vote on another ticket, not relevant to my request.  

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

1,179 views 16 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you