Bug #16490

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

Added by Lucas Di Pentima 4 months ago. Updated 13 days 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.

History

#1 Updated by Lucas Di Pentima 4 months ago

  • Target version changed from 2020-07-01 Sprint to Arvados Future Sprints

#2 Updated by Lucas Di Pentima 4 months ago

  • Status changed from New to Rejected

With the principle of least surprise, we decided that wb2's behavior is correct and it should give the user the opportunity to fix the name when there's a duplication.

#3 Updated by Ward Vandewege 13 days ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF