Contributor and floating developer license

The floating license will be requested when the user tries to do something that requires a developer license.

Dan Kogan

Hi, if a user has been assigned both a contributor and a floating
developer license when will the floating license be requested?

Will it be when the user logs in, making the assignment of the
contributor license redundant; or will it be when the user tries to do
something that requires a developer license?

Many thanks,
Jeremy

Dan, thanks. This is what I expected. However, I've just taken a look at
the 'Issued Floating License Leases' page for floating developer
licenses and see that most of the users have gained a floating license
in order to execute the operation called:

com.ibm.team.dashboard.viewPersonalDashboard

The list includes me. I understand from the docs that I need a dev
license to create a personal dashboard, but I'm curious as to why I need
a developer license to view a personal dashboard. I don't recall
changing it ever. I can remove my floating license, so I only have a
contributor license and can still view my personal dashboard.

In addition, even without a floating dev license, I can create a
personalized dashboard from the web UI.

So I think I have two questions now:

Why do I need a developer license to view a personal dashboard?

Why do I not need a developer license to create a personal dashboard? -
this is contrary to the the infocenter:
https://jazz.net/jazzdocs/topic/com.ibm.team.concert.doc/topics/c_rtc-editions.html

Thanks,
Jeremy

On 06/01/2009 15:28, dkogan wrote:

The floating license will be requested when the user tries to do
something that requires a developer license.

Dan Kogan


hughesjwrote:
Hi, if a user has been assigned both a contributor and a floating
developer license when will the floating license be requested?

Will it be when the user logs in, making the assignment of the
contributor license redundant; or will it be when the user tries to
do
something that requires a developer license?

Many thanks,
Jeremy

There is a known issue where the viewPersonalDashboard will incorrectly
cause licenses to be checked out. As to the ability to create a
personal dashboard without a developer license, that is a good question
for the Dashboard team, perhaps it is a bug, or a modified behavior that
didn't get reflected in the doc.

-
Matt Lavin
Jazz Server Team


On Tue, 2009-01-06 at 19:46 +0000, Jeremy Hughes wrote:

Dan, thanks. This is what I expected. However, I've just taken a look at
the 'Issued Floating License Leases' page for floating developer
licenses and see that most of the users have gained a floating license
in order to execute the operation called:

com.ibm.team.dashboard.viewPersonalDashboard

The list includes me. I understand from the docs that I need a dev
license to create a personal dashboard, but I'm curious as to why I need
a developer license to view a personal dashboard. I don't recall
changing it ever. I can remove my floating license, so I only have a
contributor license and can still view my personal dashboard.

In addition, even without a floating dev license, I can create a
personalized dashboard from the web UI.

So I think I have two questions now:

Why do I need a developer license to view a personal dashboard?

Why do I not need a developer license to create a personal dashboard? -
this is contrary to the the infocenter:
https://jazz.net/jazzdocs/topic/com.ibm.team.concert.doc/topics/c_rtc-editions.html

Thanks,
Jeremy

On 06/01/2009 15:28, dkogan wrote:
The floating license will be requested when the user tries to do
something that requires a developer license.

Dan Kogan


hughesjwrote:
Hi, if a user has been assigned both a contributor and a floating
developer license when will the floating license be requested?

Will it be when the user logs in, making the assignment of the
contributor license redundant; or will it be when the user tries to
do
something that requires a developer license?

Many thanks,
Jeremy

This was an unintended side effect of the way we're differentiating between the Express and Standard versions - based on which operations are allowed.

We are working to resolve this problem, see:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/62596