-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🚨🚨 Source JIRA: Save state for Boards Issues per board (#33715)
- Loading branch information
Showing
6 changed files
with
97 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Jira Migration Guide | ||
|
||
## 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: | ||
|
||
1. Select **Connections** in the main navbar. | ||
1.1 Select the connection(s) affected by the update. | ||
2. Select the **Replication** tab. | ||
2.1 Select **Refresh source schema**. | ||
```note | ||
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. | ||
```note | ||
Depending on destination type you may not be prompted to reset your data | ||
``` | ||
4. Select **Save connection**. | ||
```note | ||
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](https://docs.airbyte.com/operator-guides/reset). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters