New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 633305 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Feature



Sign in to add a comment

Feature request: alias names for workspaces

Reported by remysh...@gmail.com, Aug 1 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36

Steps to reproduce the problem:
1. Use common directory structure across projects
2. Add multiple projects to devtool workspaces
3. Get confused as to which one is which - see screenshot:

https://cldup.com/X95mCcnxfU.png

What is the expected behavior?
If it were possible to add an alias (or select a different label for the shown directory in the tree view).

What went wrong?
It's unclear which folder belongs to which project because they all have a common root, in this case "public".

Did this work before? N/A 

Chrome version: 52.0.2743.82  Channel: stable
OS Version: OS X 10.10.3
Flash Version: Shockwave Flash 22.0 r0
 
Labels: -Type-Bug Type-Feature
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
Owner: lushnikov@chromium.org
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 12 2017

Status: Fixed (was: Assigned)

Sign in to add a comment