There is currently an option to approve outgoing changes or incoming records, but not incoming changes.
The current options are:
- Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to Features) or
- Select one-way mapping only and potentially end up with mis-matched Aha and Jira records
For the one-way mapping we could periodically force Jira to take the Aha data to keep things in sync, but this may end up losing data in Jira that we did want to keep.
|Release time frame|