Map a custom field (on any layout) to an issue field in Jira (for our purposes, other institutions will have different integrations) where the population of that field occurs in a single direction (Jira to Aha!). Once populated in Aha!, only the integration should have the ability to update it. This makes it read-only to the Aha user but amendable by the integration user. Perhaps this could be achieved with an additional choice in the mapping options (single direction, one-way edit)
|Release time frame|
Thank you for your idea. As noted, it is currently possible to map fields to sync one-way to or from the development system. When this is done the field will be kept in sync by subsequent updates. So if a field that is mapped one way from the development system to Aha! is updated in Aha!, that update will be overwritten the next time any change is made to the issue in the development system.
Given the current functionality and other priorities, we are unlikely to implement this idea at this time. We hope you can understand.