Aha! uses email addresses to match Aha! users to Jira users. If Jira does not supply a user’s email address in the integration webhook or API, Aha! will now display an error message showing you how to fix the issue or disable the field mapping.
Click any of the following links to skip ahead:
- Solution 1: Email mismatch
- Solution 2: Jira user permissions
- Solution 3: Hidden email addresses in Jira
- Solution 4: Jira email visibility
- Other issues
Solution 1: Email mismatch
Whenever you run into an issue where an assignee is set in Aha! but does not properly get set in Jira, the first thing you should check is that the email addresses are matches.
The Jira API relies on an email address map when setting users, either as an issue assignee or the issue reporter. The assignee or reporter fields must be on the Create issue and Edit issue screens for Aha! to actually write these values.
Note: The integration will use the user's full name if Jira is configured to not show email addresses.
Solution 2: Jira user permissions
Email address matching is what causes the majority of problems here. However, sometimes the email addresses do match but the reporter or assignee fields still do not set.
If this is the case, you want to verify that the user the Jira integration is configured to run as actually has permissions to browse users in Jira.
A user can be configured in Jira without the permission to browse other users. In that case, the integration will fail to properly set the assignee or reporter since the user does not actually have any type of visibility into who the other users are in the Jira account.
To test this:
- Log into Jira as the integration user and trying to assign a feature to the user in question.
- Or, run a simple API call in your browser:
- While logged into Jira as the integration user, paste the above into your browser window.
- Replace the "yourdomain.atlassian.net" part with your Jira domain for either Cloud or Server implementations.
- Replace the firstname.lastname@example.org with the email address of the user you are trying to assign the issue to.
- Hit enter. If your integration user has proper access, this call should generate a positive result listing out the information on the user in question.
Solution 3: Hidden email addresses in Jira
There is one final Jira configuration that can lead to assignee not working even with correct email addresses.
You may have a situation where the user/picker?query command returns nothing for your email but does successfully return if you use your username instead. In this situation, you may have a Jira account configuration setup where email addresses are hidden.
This is a setting under System > General configuration.
Solution 4: Jira email visibility
In compliance with GDPR restrictions, Atlassian has been updates to user information passed through their API. Specifically, they no longer pass a user's email address through the webhook payload unless users specify in their profile settings that their email address can be visible to Anyone.
To make this change, log in to Jira and open your Profile and visibility page. Then set your email address's visibility to Anyone.