Has anyone else noticed that the reporter’s email address is no longer displayed when hovering over their name in a JSM work item?
We first noticed this change within the past few days or week. While it isn’t a deal breaker, the hover detail was very useful for quickly identifying which organization a customer belonged to based on their email domain.
This is particularly helpful because the Organizations field does not always populate automatically (a known issue we occasionally encounter in JSM).
Has anyone else seen this change? Does anyone know whether it was intentional, and is anyone else hoping Atlassian restores the email address to the reporter hover card?
Hello @Chris Green
Somebody asked about that before Solved: Customer Email address not showing on work item vi...
It depends if they are just Portal Only or Accounts because some things like email privacy can be restricted by them.
Historically there was couple Regressions around that, so probably will be good to adress that with Atlassian.
It does look like it was updated recently but on my end I still see an email shown for the customer/reporter in a line under the name and title of the customer (in the area of your first blacked out box)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My too but it's not consistent.
That on a side, with this all UI changes last and this year hard to follow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The inconsistency Arkadiusz describes has a cause that sits outside JSM, and it's separable from the question of whether something changed.
It's an account setting. Email address visibility belongs to the individual Atlassian account, not to JSM or the project, and the holder controls it at id.atlassian.com/manage-profile/profile-and-visibility, where email sits alongside profile photo, location and local time as a field they pick an audience for. So two reporters on the same project can render differently with nothing configured differently on your side. That's the expected shape.
There's a second split that matters more for what you're actually doing, because it depends on where you are looking rather than on who the customer is. In the admin screens the setting doesn't apply to you: "Your email address is always visible, no matter its visibility setting, to organization admins, user access admins and site administrators when they're managing users in the Administration screens." Inside the product it does: "Visibility settings for all other fields, including the email address field, are applied when organization admins, user access admins and site administrators collaborate with you within Atlassian apps." A work item is the second case and the user list is the first, so an address the hover card won't give you is still readable from the user list in admin.atlassian.com. Clumsier than a hover, but it survives whatever the card does.
None of that explains an address disappearing for reporters who haven't touched their own profile, which is the part you actually noticed. Only that one is a regression. The evidence that separates it cleanly is a customer whose visibility is set to Anyone and whose address still doesn't appear.
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.