Project

General

Profile

Actions

Bug #16490

closed

Projects & collections creation fail when trying to use a preexisting name

Added by Lucas Di Pentima about 2 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-
Release relationship:
Auto

Description

Now that workbench2 takes the user to a newly created object, asking for ensure_unique_name: true shouldn't be so confusing, and also the behavior would be consistent with wb1.

Although this fix seems super trivial, some code reading revealed that it will require a service layer refactoring because the service API currently doesn't allow passing optional data that's not part of the object being created.

Actions

Also available in: Atom PDF