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.
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 and have the permission to browse other users left off, that will then cause the integration to fail in properly setting 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.
You can test this by simply logging into JIRA as the integration user and trying to assign a feature to the user in question. Or you can 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 it should generate an positive result listing out the information on the user in question.