Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Dec 8, 2022
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit URBANCODE-I-512 Cleanup restriction to block possibility of change cleanup settings by users..

Urbancode Deploy - Artifact cleanup Merged

Hi Team,

Creating this idea again as my latest comment on I-484 was not visible and I474 URL is not working.

Combining both requirements around artifacts together -

Requirement - 1

Urbancode Deploy - Add Role based Team Permission for Artifact Cleanup


Please provide a role based permission for artifact cleanup on the component, environment level as well.For a large enterprise, it is very difficult to check and control what files are being uploaded by various app dev teams and how many snapshots are created. Teams can still override the system settings by individually updating the values for components and environment snapshots retention limit. We would like to globally control this value and not allow teams to override this setting so cleanup policies are followed as required. Thanks.

Requirement - 2

Hi Osman,

I am not able to provide more details under comment section for this idea. It looks like it's blocked being a duplicate.

Questions -

  1. Could you please share the link for 474 here? It's not working for me

2. Just to elaborate more on the requirement of this idea - Can IBM add a UI functionality through which we can delete any old archives before a specific year? We have to keep archives for 7 years to follow the retention policy. Please also consider the scenario if something was archived -> unarchived -> archived again then it would take the new archived timestamp.

Please let me know if you need more details. Thanks.

Idea priority Urgent
  • Admin
    Osman Burucu
    Apr 12, 2023

    First part of Article series was published which covers general archive handling

  • Admin
    Osman Burucu
    Mar 13, 2023

    Thank You for your feedback.

    Please could you check the latest version 7.3.0 with the clean up configuration page to verify. I to think that it will help you tremendously.

    I also will check with development and reply as soon as i know more.

  • Guest
    Mar 13, 2023

    For handling cleanup outside of UCD -

    I believe IBM doesn't recommend touching the file system from the backend. Is this something officially documented somewhere? If not, I would recommend to please consider this again or provide an alternate solution that helps us resolve this problem with no issues from vendor support side.

    For new cleanup settings feature -

    The problem is how to restrict these changes by not letting users to modify cleanup settings on components or environments. The best would be to keep this option with tool admins only. I am not sure how this feature will help us in achieving that. We have about 30k components, 6k applications with minimum 3 environments in each. Filtering on so much data will impact the performance.

    I believe UCD team should think about first restricting the control on systems settings and for the new feature offered it should be more based on TYPE (so for e.g., enterprises with data retention policies for PROD) can have prod deployed artifacts for say 7 years. Thanks.

  • Admin
    Osman Burucu
    Feb 14, 2023

    Regarding the clean-up of archive files:

    this can be always handled outside of UCD. You can use your company wide archiving and backup system to move "old" files into your archiving system and remove it from the file-location defined for UCD.

    If a restore is needed of the given archive, just place it back there, use the UCD function for restore.

    As the UCD function will always create a new version internaly, the next archiving of the artifacts will also generate a new file, which you again can backup and restore on demand

  • Admin
    Osman Burucu
    Feb 14, 2023

    We do provide the capability to check and edit the cleanup settings with a new feature "Cleanup configurations" (see doc:

    For this we do provice permission setting in the role configuration:

    Bulk Manage Cleanup

    Allows users to view, and edit the cleanup settings of multiple components and environments from the Cleanup Configuration page.

    A given role (which has the right to change this values) could check and overwrite the wrong values from there.

    Adding more permission settings down to artifact level will increase complexity tremendously.

    This is related to RFE URBANCODE-I-512

    Please add your feedback to it