Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Displaying images in email content #6036

Closed
ramyaragupathy opened this issue Aug 22, 2023 · 3 comments · Fixed by #6312
Closed

Displaying images in email content #6036

ramyaragupathy opened this issue Aug 22, 2023 · 3 comments · Fixed by #6312

Comments

@ramyaragupathy
Copy link
Member

Is your feature request related to a problem? Please describe.
From slack -

image

Describe the solution you'd like
Ideally an image should appear in the email body instead of markdown content

@Aadesh-Baral
Copy link
Contributor

Up until now, I have not been able to replicate this problem in both my local setup and the staging environment. In my testing, markdown content is converted to HTML and then displayed as an image.

test_all_contrib_message

@Patrik-Br
Copy link

I am one of the users who received the messages from Jana in past and I can confirm that in some messages it shows the image and in some it doesn't (it will show the markdown content message instead).
image

I tried to replicate it on the staging site, even using the exact same image but I wasn't able to replicate the issue.

@Patrik-Br
Copy link

Patrik-Br commented Oct 11, 2023

Yesterday I was validating tasks during a mapathon. Sometimes I am including screenshots in my feedback message in task comment and today one of the users told me that they had this exact same issue. I sent them a screenshot (image) and they saw the URL instead.

So I am reporting that this issue is not only for messages sent by project managers but in all types of notifications in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants