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 Under review
Workspace Targetprocess
Categories Other
Created by Guest
Created on Nov 3, 2025

When splitting Features, the Agile Release Train and/or Team assigned to the original Feature being split should also be assigned to the new Feature created by Feature split

Today we have a Validation Rule in M&T's Targetprocess environment that keeps Features from being created without an ART and/or Team assigned. This is prohibiting users from being able to split Features that only have an ART assigned because the ART assignment is not carried into the newly created Feature as result of the split. The purpose of the validation rule is to ensure Features created in Targetprocess have a Jira project to map back to via ART or Team assignment, so we cannot disable the Validation Rule without risking having orphaned Features in ATP.

We would like for the Agile Release Train assignment to the Feature to be carried over to the newly created Feature (created from split) so that we don't have to disable the Validation Rule that ensures no Feature is created without a home in Jira (ART or Team assignment).

Idea priority High