Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I've noticed since JIRA was updated yesterday that all ticket notifications from JIRA to my email Inbox have three huge Atlassian logos attached.
How does one block them? They cause a lot of additional and unnecessary scrolling.
Thanks,
Melissa
Hi Melissa,
The case is still being investigated and for now, we were not able to reproduce on our end.
A bug was raised for our dev team to check and fix the issue.
- https://jira.atlassian.com/browse/JRACLOUD-70795
All updates will be posted on the bug, so please, click on vote and watch to receive the updates.
Regards,
Angélica
Hi Melissa,
I've tested on a test instance and the notifications are not showing different Atlassian logos.
Can you please send us a screenshot of the notification that has this logos?
Is it notification for "Issue created" or is it another specific notification?
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is a screenshot of one email notification:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Melissa,
Thank you for the details.
I've tried to reproduce this error, but I wasn't able to.
Just for us to check what is happening, can you please open the notification on Gmail and select the option "Show original"?
On this page you will see the header of the message, then search for Content-Disposition: inline.
It will look like this:
Can you send us a screenshot of this information?
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Melissa,
I believe that the best option to try to reproduce this error is by accessing your instance in order to create a test ticket and adding our email to receive the notification, so we can check if the same behaviour will happen.
I've created a ticket on our behalf with our support and I'll be watching until the issue is resolved.
If you have any other information that you want to add, please let us know.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.