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 Submitted
Workspace Targetprocess
Categories User Experience
Created by Guest
Created on May 13, 2026

The same underlying date field is exposed under different names in Apptio Targetprocess Request Entity —“Completion Date” in the UI, “Finished” in lists, and “EndDate” in filters—and this inconsistency is by design and not currently configurable.

Why it’s useful

  • Clarifies that the naming inconsistency is out‑of‑the‑box behavior, not a misconfiguration by your team.
  • Prevents wasted effort trying to rename or standardize fields that cannot be unified today.
  • Establishes the correct field names to use in each context, especially for filtering logic.

Who would benefit

  • Advanced users, report builders, and data consumers who create views, filters, and metrics.
  • Admins and platform owners who support teams and need to explain “why the same date looks different depending on where you are.”
  • New users who often assume the fields are different when they are actually the same.

How it should (ideally) work

  • A single, consistent display name across UX, lists, and filters to reduce cognitive load.
Idea priority High
  • Guest
    May 13, 2026

    If IBM asks which name should be the standard, I feel it should be 'Enddate' for the simple fact that APIs use that value.  The down stream changes would be minimal.