What is the challenge? |
When assigning features in Aha that are then sync'd to Jira - the assignee field cannot be set |
---|---|
What is the impact? |
When development teams use Jira and Product teams use Aha, the feature becomes the common currency. The development team can see who the product person who is 'owning' that feature especially if they working with multiple stakeholders. |
Describe your idea |
In the Jira integration field mappings allow the Assignee to be set. the source Aha field may depend on the way users are set up but most Jira configurations use email address, even those with SSO. The email address would allow the common value to be used to sync that data |
The assignee field can be mapped and synced with Jira.
To configure this:
Update the integration mappings to include assignee:
Ensure the user in Jira also has a matching user in Aha! Roadmaps. They can have a Reviewer or Viewer permission, but we do the mapping based on the assignee field and email address.
Please reach out to us at support@aha.io if you have any questions.