Bug 1328122 - Unable to edit project details when you own both personal and group project with same name
Summary: Unable to edit project details when you own both personal and group project w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Kadlčík
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 14:06 UTC by Jakub Kadlčík
Modified: 2016-05-05 13:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-05 13:06:39 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1328129 0 unspecified CLOSED Unable to create personal project when you already own group project with same name 2021-02-22 00:41:40 UTC

Internal Links: 1328129

Description Jakub Kadlčík 2016-04-18 14:06:59 UTC
Description of problem:
You are not able to edit your project details when you own both personal and group project with same name.

Version-Release number of selected component (if applicable):
copr-frontend-1.86

How reproducible:
Always

Steps to Reproduce:
1. Create personal project called "foo"
2. Go to arbitrary group that you are member of
3. Create project called "foo" in this group
4. Edit your personal "foo" project and hit "Update" button

Actual results:
You receive following error message: "You already have project named 'foo'."

Expected results:
Successful update of the project

Additional info:
If you try to edit your group project in step 4, you will succeed. The fail occurs only when editing your personal "foo" project.

Comment 1 Jakub Kadlčík 2016-04-19 12:13:17 UTC
Modified in: e33f762

Comment 2 Miroslav Suchý 2016-05-05 13:06:39 UTC
Package including this fix has been deployed on production instance of Copr.


Note You need to log in before you can comment on or make changes to this bug.