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 Future consideration
Categories ClearCase
Created by Guest
Created on Aug 5, 2016

reqmaster should (optionally) transfer mastership of attached hyperlinks

We propose the following extension to the "multitool reqmaster" command:
multitool reqmaster -hlink [ -hltype type1,type2,... ] { brtype:name | path@@branch-instance }

Default behavior (without -hlink): request-for-mastership will transfer only the mastership of the object(s) specified as arguments. This is the same behaviour as with ClearCase and before.

Option -hlink: If specified, change the mastership of any hyperlinks attached to the objects for which mastership is requested; the hyperlink mastership is changed only if: a) the mastership of the given object can be successfully changed as requested and b) the hyperlink is mastered by the same replica as the requested object (before the mastership change). After all mastership changes are applied, send all these changes to the requesting replica (like in the current ClearCase versions)

Option -hltype : only valid with option -hlink; allows to limit the mastership change to the given list of hyperlink types; mastership of other hyperlinks attached to the requested object is left unchanged.

Note: since this proposal implies a change in cross-site RPC calls (reqmaster), a new feature level may be required. If so, it is accepted that it comes only with a new major or update release, i.e. 10 or 9.1).

Idea priority Medium
RFE ID 92644
RFE Product Rational ClearCase
  • Guest
    Aug 22, 2016

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.