In 3.0.1, to my knowledge, the bridges just require that you have read
access to the two objects connected by the Bridge. So in the case of
the CQ Bridge, you need read access to the work item in RTC and read
access to the record in CQ. A stakeholder license should give you read
access to the work item (but you will of course also need a CQ license
that gives you read access to the CQ record). In the case of the CC
Bridge, you need read access to the work item in RTC and read access to
the CC UCM activity or to the base CC version.

But note that the licensing story has evolved with each release, so the
situation with 2.0 is probably different (and possibly, somewhat
different in 3.0). Anyone out there have more definitive knowledge?

Cheers,
Geoff

On 5/3/2011 5:08 AM, theju wrote:

One quick question:
Is anybody using a stakeholder license with ClearCase and ClearQuest
bridge? Except for no-access to build management and reporting
features is there any other constraint with stakeholder license used
with CC and CQ bridges? Please let me know.

Thanks!

If you are using ClearCase as the SCM solution (linking to work items
via the CC Bridge), then you would not be creating any repository
workspaces in RTC (a repository workspace is only used by someone using
RTC-SCM as their SCM solution).

Cheers,
Geoff

On 5/4/2011 7:08 AM, theju wrote:

Can a developer holding a stakeholder license use RTC for development
work with ClearCase as the SCM solution using the bridge? The reason
I'm doubting is with stakeholder license I can't even create a
repository workspace in RTC!

Thanks!