escalated ticket Jira link not generated
ART-2053_KNOWLEDGE_NODE-66
not assigned to any epic in Jira and after updating the issue in Jira and forward syncing the issue in DevRev defaults to the default part.\n* AirSync extracts all links that are related to synced items. These links can link synced items with non-synced items. In this case the link creation is skipped and the report shows these links as skipped.\n* In the forward sync, AirSync creates parent-child links taken from Jira parent fields. So for example, if a subtask has a parent task, a
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-2053_KNOWLEDGE_NODE-63
type is PAT based. When creating a PAT, the user can specify the expiration date. For long running migrations, it is recommended to set the PAT to never expire, as on expiration, the PAT must be recreated manually in Jira.\n\n### Updates\n\n* If a Jira field is not writable in the creation or edit screen, AirSync may fail to create or update that issue in Jira with the corresponding change in DevRev.\n* If there is no direct transition from the current issue state to the next state in Jira, the
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-2053_KNOWLEDGE_NODE-46
used. The subtype format is as follows: \\_jira\\\\_{jira\\\\_site}\\\\_{jira\\\\_project\\\\_name}\\\\_issues.{type}\\_. For example, if you want to sync to a Bug to a Jira project called **Maple** that's served through [https://devrev.atlassian.net](https://devrev.atlassian.net/), this would show as \\_jira\\\\_devrev.atlassian.net\\\\_maple\\\\_issues.bug\\_.\n\nAfter a DevRev work item has been marked for syncing, it's created in the specified Jira project the next time the [Sync from
Jira Software AirSync | AirSync | Snap-ins | DevRev
ART-2053_KNOWLEDGE_NODE-52
permissions for successfully importing a Jira project\n\nThese permissions are required for a successful import:\n\n* **Browse projects**: The user making the connection needs this permission for the projects they want to sync. It is advisable to check beforehand if they can browse the issues in the project they wish to bring into DevRev.\n* **Create issues**: Jira not only requires this project scoped permission to create issues, but also to extract issue types. This is a must-have permission
Jira Software AirSync | AirSync | Snap-ins | DevRev