Project

General

Profile

Actions
Copy link

Bug #16490

closed

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

Added by Lucas Di Pentima almost 4 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assigned To:
Lucas Di Pentima
Category:
Workbench2
Target version:
-
Story points:
-
Release:
Workbench 2 Backlog
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
Copy link
 #1

Updated by Lucas Di Pentima almost 4 years ago

  • Target version changed from 2020-07-01 Sprint to Arvados Future Sprints
Actions
Copy link
 #2

Updated by Lucas Di Pentima almost 4 years 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.

Actions
Copy link
 #3

Updated by Ward Vandewege over 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link

Also available in: Atom PDF