Jira Migration Guide
Upgrading to 2.0.0
Note: this change is only breaking if you are using the Issues, Boards Issues or Sprint Issues streams in Incremental Sync mode.
This is a breaking change because the migration to low-code will result in incremental stream states changing their format by saving them per partition. Additionally, an issue in the Project Avatars stream has been fixed, where a field was defined as 'project_id,' when in reality, it holds a project key (now it holds project id). Please follow the instructions below to migrate to version 2.0.0:
- Select Connections in the main navbar. 1.1 Select the connection(s) affected by the update.
- Select the Replication tab.
2.1 Select Refresh source schema.
Any detected schema changes will be listed for your review.
2.2 Select OK. 3. Select Save changes at the bottom of the page. 3.1 Ensure the Reset affected streams option is checked.
Depending on destination type you may not be prompted to reset your data
- Select Save connection.
This will reset the data in your destination and initiate a fresh sync.
For more information on resetting your data in Airbyte, see this page.
Upgrading to 1.0.0
Note: this change is only breaking if you are using the Boards Issues stream in Incremental Sync mode.
This is a breaking change because Stream State for Boards Issues will be changed, so please follow the instructions below to migrate to version 1.0.0:
- Select Connections in the main navbar. 1.1 Select the connection(s) affected by the update.
- Select the Replication tab.
2.1 Select Refresh source schema.
Any detected schema changes will be listed for your review.
2.2 Select OK. 3. Select Save changes at the bottom of the page. 3.1 Ensure the Reset affected streams option is checked.
Depending on destination type you may not be prompted to reset your data
- Select Save connection.
This will reset the data in your destination and initiate a fresh sync.
For more information on resetting your data in Airbyte, see this page.