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 (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 Not under consideration
Workspace Rational Other
Categories Build Forge
Created by Guest
Created on Jul 15, 2016

Fix required : Not able to restart RBF job from GUI, when the job is triggered as 'API-Only' user

Issue : When the RBF job which gets triggered from API as "API-Only" user fails, we are not able to restart the job from GUI as "normal" user.
Note: GUI is logged in as 'normal' user

Work around TSR provided : Use SQL to update the build ownership to a normal console user in the database and restart the build via console UI

Challenges with the workaround :
1. We need to get RBF server backend access and RBF DB schema access for all the GUI users (deployers) which is not recommended
2. It is very difficult to execute the query for every failed job

What we expect : A solution to restart the failed jobs without running DB query
Other Concerns : Currently we are running on RBF version 7.1.3.3. We have approximately 300+ RBF agents. If the Fix for the issue is provided in next release(probably version 8.0.0.x), we will have difficulty in upgrading RBF to 8.0.0.x version since upgrading all 300+ agents to 8.0.0.x version is a huge effort. Hence the fix is expected to be a patch in the exiting RBF version.

Idea priority Medium
RFE ID 91558
RFE URL
RFE Product Rational Build Forge
  • Guest
    Sep 16, 2022

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, the age of the RFE suggests it is outdated or has been delivered over the time, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Dec 10, 2020

    The feature that is described in this request is a candidate for a future release.