JMWE post function "Email Issue" does not expose user names anymore?

Paul Alexander

I use the JMWE post function called "Email Issue". I use Atlassian Cloud. In the body of the email, I use a nunjucks function called roleMembers (under Jira Users and Groups) formatted like this. It has worked for about year, but has recently changed. What once displayed the member's login names associated with the role now only returns the big long accountId for each user. Not useful or helpful. I know there is user security and all, but what gives?

 

{{'Production Support' | roleMembers | join(',')}}

// old response

pjones

// new response

accountId:557058:b6c13fe2-xxxx-xx-x-x--xx-x-x-x-x-x--x-x-x

David Fischer

Hi Paul,

unfortunately, this is part of the big GDPR changes that Atlassian is (slowly) rolling out on all their Cloud apps. Usernames and user keys are going away completely, and replaced with a unique, opaque accountId. Even email addresses will become inaccessible by default (unless users explicitly make them visible, in an upcoming Privacy control user interface).

In your case, you might want to display the role members' "display name" instead. Unfortunately, this is not currently available in the roleMembers filter, but this is a good idea and we'll release an improvement soon.

In any case, you really need to read this: Spring 2019 breaking changes for GDPR . We sent out an email to all of our customers about this, and we are working with Atlassian to also send an in-product message to warn everybody about the changes.