Add new Location field to all items to capture item location information
Options
Victor Cheung
Member, Data Exchange Posts: 90
Request: Add new "Location" field to all items to capture location information
Description: This new "Location" field is more like a native attribute or property that all item types will have and will display the qualified current location of the item within the project.
Benefit: For large projects consisting of hundreds of items and many users from different teams contributing to a small portion of the project, not everyone will be familiar with all items within the project. Therefore, it will help greatly in all views/pages that can have configurable fields displayed to also have the ability to show the item's location information (i.e. parent folders) to provide crucial context. Some examples of the views that would benefit by this would be Trace View (to get a better sense of what those upstream/downstream related items actually are), the synchronized items view, reviews, etc.
Suggestion: Because this "Location" field is more like an attribute or property of every item, it should be read-only. It also be dynamic and always reflect the correct location information when items are moved, when folders are renamed, when folders are deleted/added. To address verbosity/redundancy -- the level of "qualified-ness" should be configurable -- that is, say by default, the Location field will display every level of component/set/folder beginning with the Project node -- however, ideally users would be able to adjust the beginning to leave out, say, the Project node and/or the first component item, or display beginning from the first set item, etc. (i.e. displaying the fully qualified location context can quickly be too verbose).
Similar topic thread:
https://community.jamasoftware.com/communities/community-home/digestviewer/viewthread?GroupId=7&MID=349&CommunityKey=4eac21f6-24d1-4f1e-92bd-76860b52af2c&tab=digestviewer#bma961061e-c20d-419a-a5af-0e8b7bf59db4
Thank You!
Description: This new "Location" field is more like a native attribute or property that all item types will have and will display the qualified current location of the item within the project.
Benefit: For large projects consisting of hundreds of items and many users from different teams contributing to a small portion of the project, not everyone will be familiar with all items within the project. Therefore, it will help greatly in all views/pages that can have configurable fields displayed to also have the ability to show the item's location information (i.e. parent folders) to provide crucial context. Some examples of the views that would benefit by this would be Trace View (to get a better sense of what those upstream/downstream related items actually are), the synchronized items view, reviews, etc.
Suggestion: Because this "Location" field is more like an attribute or property of every item, it should be read-only. It also be dynamic and always reflect the correct location information when items are moved, when folders are renamed, when folders are deleted/added. To address verbosity/redundancy -- the level of "qualified-ness" should be configurable -- that is, say by default, the Location field will display every level of component/set/folder beginning with the Project node -- however, ideally users would be able to adjust the beginning to leave out, say, the Project node and/or the first component item, or display beginning from the first set item, etc. (i.e. displaying the fully qualified location context can quickly be too verbose).
Similar topic thread:
https://community.jamasoftware.com/communities/community-home/digestviewer/viewthread?GroupId=7&MID=349&CommunityKey=4eac21f6-24d1-4f1e-92bd-76860b52af2c&tab=digestviewer#bma961061e-c20d-419a-a5af-0e8b7bf59db4
Thank You!
victor
0