Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Future consideration
Categories Administration
Created by Guest
Created on Mar 16, 2022

End User cannot move artifact to another folder without having DELETE permission

End Users should never have the ability to delete an artifact, but the delete permission must be assigned in order to allow end-user to move artifacts between folders. As a result, Jazz admins with super-admin permissions are being called upon to do a simple task to move artifacts between folders, which cause a productivity decline.

Idea priority High
Needed By Quarter
  • Guest
    Reply
    |
    Jan 26, 2023

    This is not fixed yet, but IBM added an Advanced Property to skip the delete permission check. This allows end users to move objects to other folders if set to True. However, this works application wide, not at the project level.

  • Guest
    Reply
    |
    Nov 10, 2022

    For the comment about iFix004 to iFix015, that was a typo and I am unable to edit the comment. It should state iFix004 to iFix014. iFix 014 is what is now having issues related to this moving artifact issue.

  • Guest
    Reply
    |
    Nov 10, 2022

    We are facing the same issue. Until very recently our instance was iFix004 and we were able to move artifacts without issue (though sometimes the menu option was greyed out, we always had the drag and drop option). A few weeks ago we moved from iFix004 to iFix015 and have discovered we are now unable to move single artifacts but can move multiple artifacts at once. Since this finding came to light, to move 1 artifact we have to move 3 artifacts to a new folder, leave the artifact you wanted to move, and move the remaining 2 artifacts back to their original folder. This process is tedious and time consuming, but was sufficient as a workaround while we reached out to IBM for resolution. We then discovered our workaround is actually an unintended loophole, since all of our end user delete permissions are off. Somehow it prevents moving of single artifacts, but allows users to move multiple artifacts at a time, which IBM informed us is a glitch in the system. In working with IBM, we understand the loophole will likely be closed and we will be left with end users unable to move anything (single or multiple), but we are also unable to allow the delete permissions to be on due to internal security requirements. Having had access to artifact moving functionality on iFix004, removing the move option while delete permissions are off seems to be a design choice by IBM that was implemented in a later iFix, a choice that is now creating speedbumps to our end users' productivity and will create roadblocks when the loophole is closed and nothing that be moved.

  • Guest
    Reply
    |
    Mar 18, 2022

    This is a valid request for enhancement.
    We would need to consider adding a new "Move artifact of type x" permission and require that the user have that permission in both the source and target folder.