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 Future consideration
Created by Guest
Created on Aug 19, 2025

Support movement of files in Git

Followup from TS019921735, TS016610424 and HD-6863.

Background: Our users use Manta to scan SAS code or IFPC files stored in various Git repositories to build lineage. This is very convenient because we can block access to users to the backend (because backend access would allow users to stort/stop manta, modify binaries, and break many enterprise security policies)

This works well except if files are renamed or are reorganized in teh git repository. For example is a file foo/bar.sas is renamed to PROD/foo/bar.sas then when the workflow is rerun, Manta will not delete  foo/bar.sas and instead add PROD/foo/bar.sas. Similarly if foo/bar.sas is deleted, Manta will not notice this.

This issue happens because in a commention, there is no option to wipe out the contents of the input dir before ingestion/extraction is run.

In our ideal state, there would be a checkbox in every connection that, when enabled, will wipe out the contenet of the input DIR when ingestion scenario for this connection is run.

Needed By Yesterday (Let's go already!)
  • Guest
    Oct 8, 2025

    Hi Jakub:

    Below details are from TS019921735, hope this will help. Here you will get the connection and workflow details in Manta DEV environment.

    Issue:
    When some SAS script/file is moved from one source directory to another, Manta is unable to track its movement and represent its correct path in the lineage.

    Steps followed:
    1. Scan a git repo, folder path -> sas-grid/source-sas-files/sas-repo-v1/.
    Refer artifacts in Manta Dev
    connection: sas-file-movement-behaviour-check
    Workflow: wf-sas-file-movement-behaviour-check

    2. Move file sas-grid/source-sas-files/sas-repo-v1/sub-dir1-v1/sub-dir2-v1/sub-dir3-v1/KW_031323.sas to sas-grid/source-sas-files/sas-repo-v1/sub-dir1-v1/KW_031323.sas in the git repo.

    3. Rescan the git repo, folder path -> sas-grid/source-sas-files/sas-repo-v1/.

    Expectation:
    The expectation is that Manta lineage will show the correct path (updated path) after re-scan.

    Actual result:
    Instead of moving, the file has been copied to the destination folder(Here sub-dir1-v1) from source folder (sub-dir1-v1) (refer revision no. 1537.917 in Manta dev)

  • Admin
    Jakub Moravec
    Sep 28, 2025

    Hi Devayon, as aked during the call, could you please provide the definition of the workflow for which you are observing this problem?

    Thank you, Jakub