-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[15.0][MIG] connector_jira_tempo: Migrate to version 15.0 #82
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
10f4e62
to
82f836d
Compare
Hello @sonhd91 currently checking also the related PRs |
@sonhd91 could you remove the commit dependency? |
82f836d
to
e3603b0
Compare
I removed the commit, thank |
e3603b0
to
1b5057b
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.
1b5057b
to
266d262
Compare
@leemannd I just rebase branch, thank |
/ocabot merge nobump |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at 69f55e0. Thanks a lot for contributing to OCA. ❤️ |
Depend on: