Can you give us an update on this?

@Michel mentioned that you have "millions of users" using the integration, yet it seems that the priority for this is set very low.

Indeed. This chance is a complete oversight. Nobody is ever going to expose their email publicly just to integrate with Jira.

Commit author email is already immutable and technically it is very difficult to change in case of GDPR request. I don't see why Jira could not rely on commit author instead of user's public profile.

Hi Jira team,
Implementing this feature is a must-have feature for our Product team.
What's the approximate ETA for this fix?

Thanks,
Roman

Hello Jira team,

Do you have an ETA for this fix? The user experience of the integration between Jira and Github for our daily operations has been degraded since your recent changes. 

Is their a case number on the Github side that we could use to escalate to our account manager?

Thanks,

Benoit

Hello,
Thanks for the update. We are looking forward to hearing from you with a solution soon.
Please keep us informed. 
Best regards,
Jérôme

Hi, just to give an update of this issue, I have changed the status of this ticket to long-term-backlog to reflect the current blocker the team ran into:

• The team is still blocked by upstream dependency on Github, as our engineering leads did not have any chance to meet with their counterparts from Github to align on our responsibility in the GDPR framework. We have no clarity on whether we could secure a meeting with them any time soon.
• In the meantime, we have already reached out to the Identity team to scope a 2nd solution. However, there will be significant lead time before the Identity team could complete the design of the solution and incorporate it into their current roadmaps to deliver.

This means that we are still blocked to implement any long-term solutions to remediate the bug, therefore moving the ticket into long-term backlog. The team will escalate this risk further up and continue monitor the movement of the dependencies to push for a solution.

Thanks.

Hi, I have changed the status of this ticket back to short-term-backlog to correctly reflect what's going on at the moment:

• The team is currently blocked by upstream dependency on Github and our GDPR experts to align on our responsibility in the GDPR framework.
• In the meantime, we are engaging the Identity team to scope a 2nd solution in case the conversation with Github falls through.

Until we have conclusions from the above ongoing conversations, the team is blocked to implement any solutions to remediate the bug.

Thanks.

Hi, as the Arc team is pushing towards a long-term solution and moving this bug ticket to 'Ready for Development', I'd like to provide a bit more visibility of the progress of this issue.

As 266fee25c089 has explained the cause of the issue in the last comment, we are actively engaging with our GDPR and compliance expert to make sure that we have correctly understood and aligned on our responsibility in the GDPR framework.

After confirming the scope of our responsibility of the GDPR framework, we will move towards working with our peers to implement the capability of deleting and rectifying user data upon requests initiated via Github, so that we could fix this issue whilst being GDPR compliant.

At the meantime, the team is aware of the impact this issue is casting on our customers, and we have implemented a temporary solution to help bring back user names to be displayed in Jira. Please try follow the steps in the temporary solution (https://github.com/atlassian/github-for-jira/blob/main/SUPPORT.md#fix-users) while the team is working towards a long term solution.

Thanks.

We're currently pushing for a change that might fix this, as it may have been a misintepretation of GDPR rules.  More updates to come.

gguimaraes  This problem is twofold:

1. Github doesn't give the user's email if they set it as private, we get a fake email instead (something like `user-123456@users.github.com`).  If the user has it as public, it only returns the primary email, which is normally their personal email that they've signed up to Github with, and not their work email.
2. There was a change on the DevInfo API side (Saiyans) which now doesn't store any personal emails/avatars for things like author information/reviewers.  This is problematic as per issue 1, it's returning their personal email all the time unless this specific user is using a work specific Github account that uses their work email as their primary one.

There are multiple possible solutions, however, none of them that we (Arc team) can do through Github for Jira as this is a change within Jira that caused this issue and we cannot control how Jira uses the data we give it.  My undersanding is that they removed this functionality (without telling us, mind you) because they didn't want to deal with GDPR considerations for personal emails/avatars - I'm not sure how GDPR applies to this data coming from Github, but I digress. 

One solution mentioned by Saiyans is that the Identity team (Jira user profile team) could add a field in the profile to allow multiple emails for associative purposes (ie. developers can add their personal github email so that it associates with their profile), however, we're now forcing millions of users to add this to their profile just to get an integration working as it should out of the box.  I don't think this is good enough and would be less effort to deal with GDPR considerations instead.

All of this to say that this is completely out of our hands and we can't do anything about this without an underlying Jira API/Data change.