Sync Jira OOTB field values

What is the challenge?

Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira.

What is the impact?

Aha is meant to be the singular solution for Product teams to set their strategy and document the details of their individual work items. Without the ability to set all necessary fields in Aha, it requires the Product team to navigate multiple solutions (Aha and Jira) to create complete records.

Describe your idea

Enhance the Aha/Jira integration capabilities so that out-of-the-box fields (and their corresponding values) can bet set in Aha and bidirectionally sync.

In our case, we use the "Team" field in Jira to allocate work to a specific engineering team. Today, that field can only be set in Jira and one-way sync from Jira to Aha.

Why can't we map that field in the integration settings, and a regular field value update occurs so that we can actually set that value in Aha and both systems are in sync?