Actions
Bug #16490
closedProjects & collections creation fail when trying to use a preexisting name
Story points:
-
Release:
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