[17.0][WIP][MIG] connector_jira_tempo: Migration to 17.0 #111
Conversation
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
SilvioC2C
force-pushed
the
17.0-mig-connector_jira_tempo
branch
2 times, most recently
from
0bf1cac
to
9161be5
Compare
The Jira API handles 2 ways to work with users: using the username or the key field (but planning to migrate to anonymous accountIds). Most of the time, the key is equal to the login, however if at some point a login is changed, the key will always stay the same as the original one. The Jira API handles both username and key field, but Tempo accepts only the username.
on Tempo Cloud the validation status have changed: * in_review: added * waiting_for_approval: dropped * ready_to_submit: dropped
SilvioC2C
force-pushed
the
17.0-mig-connector_jira_tempo
branch
from
9161be5
to
2dd16be
Compare
yankinmax
approved these changes
Sep 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migration based on top of #108 and #110