Cannot find email type preferences (text/html)

Frank Groeneveld May 1, 2018

In the past I could set text as the preferred email type. This dropdown seems to have been removed. Where can I set this for my user?

2 answers

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 2, 2018

Hi Frank,

I got an update about this bug ticket.  It turns out this functionality has recently changed in Jira Cloud.  The ability to change your email format preference from HTML to Text is no longer possible in Jira Cloud as it once was.  As a result this bug ticket has been closed as 'Won't Fix'. 

Could you please tell me more about how you were using this specific functionality in Jira Cloud?  I am interested to learn more about your particular use case for this feature.

Sorry this probably is not the answer you were looking for, but please let me know more about the use here.

Thanks,

Andy

Frank Groeneveld May 2, 2018

Thanks, that's unfortunate. The use-case is that some of us use text-only mail clients, some even command line mail clients. Furthermore, one of our colleagues had text-only switched on before the interface went away and now wants to switch to html mails, but can't.

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 4, 2018

Good news everyone:

This bug ticket has been re-opened.  It appears that this change is being given some more consideration.  I am not sure exactly when this might be resolved, but I would watch that ticket of further updates.

In the meantime, I did come across another way for end users to update their own email format preferences in Jira Cloud :D   It turns out you can make a REST API call to Jira to both find your existing email format type and to change it.

Please see the REST API reference on https://developers.atlassian.com/cloud/jira/platform/rest/#api-api-2-mypreferences-get

You can then make a call like this in order to find your current setting.  I'd recommend doing this just to make sure you are making the call correctly first.  Doing a GET won't harm anything.

curl -D- -X GET -H "Authorization: Basic STRINGREDACTED" -H "Content-Type: application/json" "https://example.atlassian.net/rest/api/2/mypreferences?key=user.notifications.mimetype"


^ find your current profile setting.  Valid values for this property are either 'html' or 'text' (no quotes).   Of course for this you will need to change the URL to match your Cloud site, and you would need to follow the steps in https://developer.atlassian.com/cloud/jira/software/jira-rest-api-basic-authentication/ in order to both generate a REST API Token, and then encode a Base64 string of your username:RestToken and then use that string to replace my 'STRINGREDACTED'.


From there you can change this with a PUT command.

curl -D- -X PUT -H "Authorization: Basic STRINGREDACTED" -H "Content-Type: application/json" "https://example.atlassian.net/rest/api/2/mypreferences?key=user.notifications.mimetype" --data text

^ updates your own profile to use text formatting

I found that changing this setting does work in my test Cloud instance.   I hope this helps.

Frank Groeneveld May 7, 2018

Great, thanks!

Jesse Atkinson May 9, 2018

This worked perfectly for me. Thank you. I've no idea why they removed it. It sucks for us mutt users to deal with html emails. 😀 Thanks for posting this. 

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 1, 2018

Hi Frank,

Sorry to hear this problem has affected you.  I too have found in my Cloud instance that I can no longer edit my own email format preferences.  However I have not been able to find any clear documentation that indicates this might be an expected change.

As such I created a new bug ticket, because in my view right now, this does appear to be a bug.  Please see https://jira.atlassian.com/browse/JRACLOUD-69399  I would recommend watching and voting on this issue.  Should updates come to light or this be corrected by a code fix, I would expect this bug to be updated with more details about this problem.

Regards,

Andy

Frank Groeneveld May 1, 2018

Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events