Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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 Future consideration
Workspace Targetprocess
Created by Guest
Created on Nov 11, 2025

Enable Directional Control (Outbound/Inbound) for “Related” Relations in Integrations

Currently, in Apptio Targetprocess integrations (e.g., ADO ↔ ATP), when using “Related” as the relation type between entities (such as Feature, User Story, and Team PI Objective), the relationship is automatically displayed as both Inbound and Outbound in the Targetprocess Relations tab.

This behavior is due to “Related” being a symmetric link type, but in real-world enterprise configurations, customers often need to treat “Related” links as contextually directional, especially when modeling dependencies or relationships that should appear only as Outbound from a specific entity.

Business Impact

This limitation reduces flexibility and clarity for portfolio and ART-level reporting.
For example:

  • When a Team PI Objective is linked to a User Story via “Related,” it appears on both sides (Inbound/Outbound), even if the business rule or reporting requirement only expects it to show as Outbound under the User Story.
  • This leads to confusing or duplicated data in reports and dashboards that use the Relations source type.
  • The only current workaround is to use Successor/Predecessor links, which may not align with how clients model “Related” work items in Azure DevOps.

Proposed Enhancement

Introduce a configuration option to control the directionality of “Related” relations within Integration settings.

Suggested features:

  1. Add a “Directional Mode” toggle for the “Related” relation in Integration Mapping:

Options:

  • Both (default)
  • Outbound only
  • Inbound only 

2. Apply the directional mode to determine how the “Related” link appears in the Relations tab of Targetprocess.

 3. Optionally, allow per-entity overrides (e.g., Feature → Related → Team PI Objective: Outbound only).

 

Expected Outcome

  • Clearer and more accurate visualization of “Related” links in Targetprocess.
  • Reduced confusion when integrating with tools like Azure DevOps that use “Related” as a common link type.
  • Better control for administrators to align relations with reporting and governance standards.
Idea priority High
  • Guest
    Nov 12, 2025

    This would be an improvement to the current set up as it does cause confusion with the current configuration

    We have PI Objectives in ADO where User Stories & Features are linked as 'related' work - when this relation syncs to Targetprocess, it shows as both an inbound and outbound relation which is confusing.