-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New workspace with the name existed in the workspaces. #36
Comments
lisyoen
changed the title
[Dashboard] New workspace with the name existed in the workspaces. #551
[Dashboard] New workspace with the name existed in the workspaces.
Oct 12, 2015
lisyoen
changed the title
[Dashboard] New workspace with the name existed in the workspaces.
New workspace with the name existed in the workspaces.
Oct 14, 2015
leechwin
added a commit
to leechwin/webida-dashboard
that referenced
this issue
Nov 18, 2015
[DESC.] webida#36 Signed-off-by: ChangHyun Lee <leechwin.lee@samsung.com>
leechwin
added a commit
to leechwin/webida-dashboard
that referenced
this issue
Nov 19, 2015
[DESC.] webida#36 Signed-off-by: ChangHyun Lee <leechwin.lee@samsung.com>
leechwin
added a commit
to leechwin/webida-dashboard
that referenced
this issue
Nov 19, 2015
[DESC.] webida#36 Signed-off-by: ChangHyun Lee <leechwin.lee@samsung.com>
Cannot create a workspace with existed name. However, there is no msg. that a project cannot created with existed name. It just do nothing. |
lisyoen
added a commit
to lisyoen/webida-dashboard
that referenced
this issue
Jan 27, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moved from webida/webida-client#551
I tried to create new workspace with the same name which other workspace already used.
PreCondition -
Workspace named 'Test' exists in the 'Workspaces' of the dashboard.
Step -
No error msg.
Nothing has been changed. Only one workspace named 'Test' exists in the workspaces.
I expected any warning/error msg. like 'The workspace 'Test' already Exist'.
The text was updated successfully, but these errors were encountered: