Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Workspace Cognos Analytics
Components Security
Created by Guest
Created on Jun 23, 2026

Audit-Compliant Report Metadata: Separate Last Accessed, Last Modified, and Last Data Refreshed Timestamps

Problem Statement
Currently, when users run a report, the metadata timestamp behavior can appear as if the report was modified, which creates confusion during internal and external audits.
For audit purposes, Last Modified should represent only actual report definition/content changes, not report execution events.

Requested Enhancement
Introduce clear and separate metadata fields for report lifecycle events:

Last Accessed Date/Time (updated on run/view)
Last Modified Date/Time (updated only when report definition/content is changed)
Last Data Refreshed Date/Time (updated when underlying report data is refreshed)
Also include corresponding user fields:

Last Accessed By
Last Modified By
Additionally, provide export/API availability for these fields to support audit evidence collection.

Business / Audit Impact

Eliminates ambiguity between report usage and report modification
Reduces audit observations and repeated clarifications
Improves traceability and control evidence quality
Supports faster closure of internal/external audit requests

Expected Outcome / Acceptance Criteria

Report execution updates only Last Accessed, not Last Modified.
Last Modified changes only on actual report definition/content updates.
Metadata fields are visible in UI and available via export/API.
Historical logs clearly distinguish access events from modification events.
Audit teams can retrieve reliable evidence without manual reconciliation.

Needed By Month