@Ksethuraj the main problem that we see with this is that the Github User has their email set to private on profile, so instead of their email we only see user@users.github.com which we can't associate with any user in Jira.

There's another secondary issue where a Github User use their personal email as their primary email instead of their work email (the one created for Jira) which means it might not associate correctly on the Jira side to an actual Jira user. We'll do our best to show the user and are currently trying to improve this experience so that we can associate multiple emails to a Jira user.

Can you please try to set the user to show their email and try again to see if it works? Thanks.

Seconding Ksethuraj -- this was definitely not a problem before.

It's admittedly been a few weeks since I last looked, but I've been relying on this feature for quite a while, and I am certain all of my authors/reviewers did not suddenly change from public GitHub emails to private. However, I can confirm the three users whose names I am able to see have public emails.

Hey all. Unfortunately, this regression is the result of a downstream team changing the way they store data. A team mate of mine is working on a doc to outline what can be done to remediate this via your GH settings, until we find a longer-term strategy.

I'll send the link through once it's ready.

Our SUPPORT docs have been updated with more info and a temporary workaround https://github.com/atlassian/github-for-jira/blob/main/SUPPORT.md#unmapped-users Unfortunately, this is not the most ideal solution but it is the best we can do at this point in time. We're trying to coordinate with the team that made the changes to see if there is a way to return this functionality for all users.

Thanks, @rachellerathbone!

Unfortunately, you're right, that's not an ideal solution. Many of my project's contributors are women or gender minorities, and making emails public opens us to harassment. What's more, the organization the project belongs to was subject to email attacks last year, where the attacker sent child sexual exploitation material to us. I can't require my contributors to publicize their emails and expose themselves to that again.

I hope you can pass this along to the upstream team responsible for this change to help them understand that not only is this change inconvenient, but it's also hostile to people who already face barriers in both the industry and open source community.

Hey @sarken. I'm really sorry to hear about what happened last year. Rest assured, our team is doing everything we can to push back on this change. I will hopefully have an update for you soon.

hello - i am also having this issue and i have not had this issue before december when apparently the change was made. i also have a private email that i do not want to show others due to security concerns.

@rachellerathbone do you have any ETA on this issue?

+1 here

https://jira.atlassian.com/browse/JSWCLOUD-23906