-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
v3 API doesn't check if a subproject relationship already exists #6271
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
Comments
Looks like we allow that on the GUI too, we only modify the queryset, but we don't really check if the subproject is valid
You can do it from the edit button, does it give you an error? |
Clicking the edit button gives me the fail whale. |
Which relationship do you want to delete? I can delete it manually for you. |
Thanks, you can delete all four. Account lf-oran, under dwproj. |
Done, let me know if it looks correct now |
It does, thanks.
…On Thu, Oct 10, 2019 at 10:18 AM Santos Gallegos ***@***.***> wrote:
Done, let me know if it looks correct now
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6271?email_source=notifications&email_token=AM3VBJNUHGPJYCNSF6MCD3TQN5PVVA5CNFSM4I7PFK22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA5DK5I#issuecomment-540685685>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM3VBJP3GLOGHPYIQBFTAWDQN5PVVANCNFSM4I7PFK2Q>
.
--
DW Talton
Release Engineering
The Linux Foundation
|
Good catch, @dwt2! Thanks for reporting this :) |
Details
Expected Result
Only one subproject relation should be allowed.
Actual Result
When creating a subproject relationship, the v3 API does not check that there is not already a relationship and will allow the creation. Also, once there is more than one relation to the same project, it can no longer be deleted via API or GUI.

The text was updated successfully, but these errors were encountered: