Booking Resources Should Have Unique Constraint on Name and Owner
Bug #1820873 reported by
Rogan Hamby
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
The issue is all in the title. I was working on a booking bug and noticed after double clicking save that it to the database two identical copies of the booking resource type. I think that names and owners combined should be a unique constraint.
Revision history for this message
| Jane Sandberg (sandbergja) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| Changed in evergreen: | |
| assignee: | Rogan Hamby (rogan-hamby) → nobody |
To post a comment you must log in.
Confirmed, you can create multiple booking resources with the same name and owner. Also, the UI should fail with a helpful error message when a user tries to make duplicative resources.