Organize components in streams in folders

EWM RFE review board has evaluated this request. This request, while valid, is unlikely to be addressed in the next 18-24 months due to other higher priority items on the Backlog. If the enhancement remains important after the time period, please open a new RFE and we will review. Although we are closing this request, it will be kept in IBM's ideas repository and may be reassessed or reopened for additional discussion in the future.We value your feedback and thank you for allowing us to partner with you in developing our products.

Trying again in a comment with hopefully better formatting:



At the moment in the Team Artifacts view, when a stream is expanded all components in this stream are immediately shown underneath.

But when an integration stream has many components coming from different applications, we would like to be able to organize these components in several folders inside the stream, depending on the application owning each component.



Hierarchical components look a bit similar visually but would not be suitable for this use case because there is no conceptual "hierarchy" in our case, and the organization needs to be independent in each stream.



To be specific, what we would like is to be able to show in the Team Artifacts view a folder in between a stream (com.ibm.team.filesystem.ui.wrapper.TeamPlaceWrapper) and a component (com.ibm.team.filesystem.ui.wrapper.TeamPlaceComponentWrapper).

And also between a workspace (com.ibm.team.filesystem.ui.wrapper.TeamPlaceWrapper) and a component (com.ibm.team.filesystem.ui.wrapper.WorkspaceComponentWrapper).



For example, for a version of an application APPA that has dependencies on components of applications APPB and APPC, we currently see:

APPA_STREAM

├ APPA_COMPONENT1

├ APPA_COMPONENT2

├ APPB_COMPONENT3

└ APPC_COMPONENT4



But we would like to be able to see instead :

APPA_STREAM

├ APPA_COMPONENT1

├ APPA_COMPONENT2

└ external dependencies

  ├ APPB_COMPONENT3

  └ APPC_COMPONENT4