-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
[13.0][MIG] connector_jira_tempo #62
[13.0][MIG] connector_jira_tempo #62
Conversation
To rebase after #60 is merged |
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.
3da6930
to
d82967c
Compare
@simahawk Rebased. If the PR is ok for you, I will just rebase and remove the fixup from @grindtildeath |
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.
LG. Squash your last commit as well
d82967c
to
9a72fc8
Compare
@simahawk Update. Thanks |
/ocabot merge nobump |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at 7856ada. Thanks a lot for contributing to OCA. ❤️ |
No description provided.