Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
5
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Standard response
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. While the idea is definitely solid, we're re-evaluating the entire JIRA notifications system, and that may entail new ways to customize emails that don't use velocity templates at all.
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
It would be very handy if, instead of adding headers like 'Subject' programmatically, JIRA let headers be specified in the email velocity templates.
This would elegantly solve a number of problems, and open new possibilities:
- Subject could be easily customized (
JRA-3568) and i18nized (JRA-4419) - We could easily make the Precedence: Bulk header removeable, for users like the ASF where this triggers spam filters
- The From: address could be customized easily (
JRA-2315) - Custom headers could be added (JRA-3933,
JRA-4440)
If this requires JIRA to parse the text to extract headers, we could read the To:, Cc: and Bcc: headers and append their values to the notification scheme targets.
Attachments
Issue Links
- is duplicated by
-
- Closed
-
- Gathering Interest
- is related to
-
- Closed
- relates to
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
JSP-263453 Loading...
