AirSync Jira Datacenter mapping error something went wrong
ART-2053_KNOWLEDGE_NODE-60
the mapping phase in the initial import, one can opt out of the permission AirSync by deselecting **Authorization Policy** option, additionally groups and group members can also be deselected. As project roles are mapped to DevRev groups, deselecting groups and group members also prevents project roles from being imported.\n\n![]()\n\nFor Jira Data Center, the permissions AirSync is not yet supported.\n\nAirSync Jira scope and limitations\n----------------------------------\n\nThe following is
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-2053_KNOWLEDGE_NODE-54
the AirSync functionality.\n\nAdminister Jira global permission is required for:\n\n* Custom field extraction - without extracting custom fields AirSync is unable to load them into DevRev, which might become problematic especially on reverse syncs if some of these fields are deemed required by Jira on issue creation.\n* User extraction (Jira Data Center only) - admin permissions are required to access the application roles, which contain the users that have access to the Jira application.
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-17232_KNOWLEDGE_NODE-3
process.\n\nThere are several reasons why some mappings might be unavailable:\n\n1. A common reason is mismatch of types. For example, if a DevRev field is expected to be `rich_text`,\n   but the field is set as `text` mapping to some fields is unavailable.\n   Refer to the [supported types](/public/airsync/metadata-extraction#declare-fields-for-each-record-type)\n   section and the general DevRev documentation for more information.\n2. Only references can be mapped to references. Ensure that
Mapping reasons | DevRev | Docs
ART-16749_KNOWLEDGE_NODE-1
request"\n}\n\nHow to Fix:\n\nRefresh the page to load the latest blueprint and status versions.\n\nComplete your field mappings again.\n\nSubmit the mappings \xe2\x80\x94 the request should now succeed.'
Troubleshooting Airdrop Mapping Error: “Something Went Wrong”
ART-16749_KNOWLEDGE_NODE-0
b'This error usually occurs when the mapping request is sent with stale data. It happens when the blueprint or status version in your browser is outdated compared to the server.\n\nTo confirm:\n\nOpen the Network tab in your browser\xe2\x80\x99s developer tools.\n\nCheck the response to the low-code POST request.\n\nResponse should look like this:{\n  "message": "recipe-manager-RecipeManagerInvalidArgument-Unspecified: blueprint or status version changed: was 9_9 on the server and 8_8 in the
Troubleshooting Airdrop Mapping Error: “Something Went Wrong”
ART-17218_KNOWLEDGE_NODE-8
|\n```\n\n[3](/airsync/initial-domain-mapping#use-the-chef-ui)\n\n### Use the Chef UI\n\n```\n|  |  |\n| --- | --- |\n| $ | chef-cli configure-mappings --env prod |\n```\n\nIf your org is not in `US-East-1`, you h ave to override an environment variable to make sure the tool reaches the right server. For example:\n\n```\n|  |  |\n| --- | --- |\n| $ | ACTIVE_PARTITION=dvrv-in-1 chef-cli configure-mappings --env prod |\n```\n\nThe options are: `dvrv-us-1`, `dvrv-eu-1`, `dvrv-in-1`, and
Initial domain mapping | DevRev | Docs
ART-17232_KNOWLEDGE_NODE-4
source system fields are correctly\n   mapped to reference fields in DevRev.\n3. Support for the `struct` type is limited. Marking a field as a struct in the metadata schema will\n   make it unavailable for mapping outside of using the custom jq transformation method.\n   Refer to the [metadata tips](/public/airsync/faq#metadata-extraction) for more information.\n4. Links are supported only on works and conversations.\n\nTransformation methods\n----------------------\n\nThe following tables
Mapping reasons | DevRev | Docs
ART-17217_KNOWLEDGE_NODE-7
file, |\n| 43 | initialDomainMapping: { |\n| 44 | /* your initial domain mapping JSON here */ |\n| 45 | }, |\n| 46 | // options: {}, |\n| 47 | }); |\n| 48 | } |\n| 49 | }; |\n| 50 |  |\n| 51 | export default run; |\n```\n\n##### \n\nYou must pass the `initialDomainMapping` parameter to\n`spawn` when running extraction phases. This ensures the correct\ndomain mapping is installed and used by the snap-in.\n\nWas this page helpful?\n\nYesNo\n\n[Previous](/airsync/manifest)[#### External sync units
Extraction phases | DevRev | Docs