-
Notifications
You must be signed in to change notification settings - Fork 8
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
codebeamer-lobster shall use CB api v3 #49
Labels
lobster-codebeamer
Affects codebeamer integration
Comments
This was referenced Jul 9, 2024
TannazVhdBMWExt
added a commit
that referenced
this issue
Jul 29, 2024
Correct the lint error Resolves #49
TannazVhdBMWExt
added a commit
that referenced
this issue
Jul 29, 2024
Correct the lint error Resolves #49
TannazVhdBMWExt
added a commit
that referenced
this issue
Jul 29, 2024
The used cb-endpoints are updated and one unit-test has been added. Resolves #49
TannazVhdBMWExt
added a commit
that referenced
this issue
Jul 31, 2024
The used cb-endpoints are updated and one unit-test has been added. Resolves #49
TannazVhdBMWExt
added a commit
that referenced
this issue
Aug 1, 2024
The used codebeamer endpoints are updated and one unit-test has been added. Resolves #49
TannazVhdBMWExt
added a commit
that referenced
this issue
Aug 2, 2024
The used codebeamer endpoints are updated and one unit-test has been added. Resolves #49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PTC strongly recommends to use codebeamer's rest api v3 instead of v1, see https://codebeamer.com/cb/wiki/117612
The new v3 has got a few advantages over v1, for example the Swagger api.
codebeamer-lobster
shall be updated to use v3 instead of v1. The changes will have no effect on the end-user, because this is an internal refactoring.This will also simplify the implementation of #47 and #50, because we don't have to implement the conversion of a field name from display name to rest api v1 name (which is camel case with lower case starting letter).
The text was updated successfully, but these errors were encountered: