-
Suggestion
-
Resolution: Timed out
-
1
-
Please check the Linked issues section of this ticket.
Docs:
- relates to
-
JRACLOUD-79775 Custom created user picker field value was empty in the email notifications when Email from settings updated to ${fullname} (mycompanyname Jira) from ${fullname} (Jira)
-
- Closed
-
-
JRACLOUD-61120 Custom email prefix per project
- Closed
-
ID-8543 Customize the sender in invitation email
- Gathering Interest
-
JRACLOUD-161 Be able to customize outgoing emails per project
- Gathering Interest
-
JRACLOUD-3933 Add custom headers to email notifications
- Gathering Interest
-
JRACLOUD-4619 Custom Fields not displayed in emails
- Gathering Interest
-
JRACLOUD-7108 Option to set sender address reply to actual user's address in email notifications
- Gathering Interest
-
JRACLOUD-7266 Provide ability to customise email templates that are used for notifications and subscriptions
- Gathering Interest
-
JRACLOUD-21888 Remove [JIRA] from email subject lines i.e email prefix in the SMTP Server config
- Gathering Interest
-
JRACLOUD-61770 Customize Filter Subscription Subject/From email
- Gathering Interest
-
JRACLOUD-62256 As a user, I want JIRA notifications to include the custom fields and their values on the Create Issue notification email
- Gathering Interest
-
JRACLOUD-70569 Allow customized emails for the notifications in Jira.
- Gathering Interest
-
JRACLOUD-80026 Update Notification Template used by Custom events
- Gathering Interest
-
JRACLOUD-82343 Allow Jira Admins to disable "Safe Internal Notification" on HIPAA-compliant instances
- Gathering Interest
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management