RELATED IDEAS
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not able to find the user based on their email address. As a result, the assignee blanks out in Aha! Roadmaps.
Suggestion:
There appears to be a solution that runs in some cases but not all, that matches Aha! users based on their name when the email address option is not enabled (perhaps this is when it isn't enabled at a server level in Jira rather than individual). Extend that to always run when email address isn't found as a backup measure.
-
-
-
-
-
-
-
-
-
-
- +2
© 2024 Aha! Labs Inc.•All rights reserved
This has been a huge issue for us. For security purposes, we don't want to enforce people to make their email addresses public. There is an article from Jira on how to get access to email addresses without changing profile settings - I believe it's intended for their third party apps. But if there is a solution for them, I would hope there would be a solution for others as well.
https://community.developer.atlassian.com/t/guidelines-for-requesting-access-to-email-address/27603
Not being able to integrate user information impacts assignee, creator, and other fields. Because of this, we can't easily use some of the Aha functionality (like capacity planning).