Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Source Control
Created by Guest
Created on Apr 26, 2022

Organize components in streams in folders

Hello,

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
Idea priority Medium
Needed By Quarter
  • Guest
    Reply
    |
    May 3, 2022

    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.

  • Guest
    Reply
    |
    Apr 26, 2022
    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