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.

Add a new idea Subscribe
Status Delivered
Workspace Targetprocess
Categories Other
Created by Guest
Created on Jun 23, 2025

RELATED IDEAS

Enable Non-Team Members to Manage Team Rosters in TargetProcess

Current Limitation:
In TargetProcess, only users who are members of a team and have the appropriate permissions can manage that team’s roster. This restriction poses a challenge for roles such as Release Train Engineers (RTEs), who are responsible for overseeing multiple teams but are not intended to be embedded within each one.

Problem Statement:
Adding an RTE to every agile team solely to grant roster management capabilities contradicts agile best practices and introduces unnecessary administrative overhead. As a result, teams have resorted to various workarounds that are inefficient, inconsistent, and difficult to scale.

Proposed Enhancement:
Extend roster management permissions to designated users—such as RTEs—even if they are not members of the team. This could be implemented via role-based access control or a configurable permission setting that allows specific users to manage team compositions without being added to the team itself.

Benefits:

  • Alignment with Agile Best Practices: Maintains the integrity of team membership by avoiding artificial additions.
  • Operational Efficiency: Reduces the need for manual workarounds and streamlines team administration.
  • Scalability: Supports enterprise-level agile frameworks where RTEs and similar roles oversee multiple teams.
Idea priority High
  • Guest
    Jul 16, 2025

    Private Preview was released to the sandbox to validate the solution that allows users with Team Edit permission in their default role to edit any team they can see.
    Users can see all teams related to the projects of a user.
    It means, users with Team Edit in their default role can edit any team related to his projects (Change team fields and assign users. Exception - Team Iteration require team membership)

    Introduces change allows:

    • Any user whose default role includes an ‘edit’ permission for a Team can now assign users or modify fields of any team they can access.
      Note: users can access any team that is linked to their projects.

    • If you need to restrict which teams a user can modify, consider using Validation Rules to enforce custom constraints.
      For example, condition AgileReleaseTrain.AssignedUser.Count(Id == $Author.Id)==0 to check if a user is a member of a Group
      Or condition TeamProjects.Count(Project.ProjectMembers.Count(User.Id==$Author.id && Role.Id in [123, 124, 122])>0)==0 that checks if a user has a certain role in the projects connected to that team.

    • Limitation: Some team’s child collections like Team Iterations and Dependencies are covered with additional permissions and require team membership.


    Global Availability release decision and ETA will clarify by October 2025


    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.