Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Unable to associate change set with work items : JazzAdmins

Hello.

A user can not associate a change set he does not own to a work item. He gets an error :
Source Control Operation (failed)

Permission demied

Problem
Permission denied during "Source Control Operation"
The user "---" does not have enough permissions on associate a Work Item to a change set owned by by an other user. The role JazzAdmins is required to perform this operation.

# In an other pop up I get
The operation is not governed by process


I searched for help and ideas. Found Unable to associate work items with change sets and Question about change sets attached to multiple work items. But is seams not to be my issue.

I can as a JazzAdmins user do this operation.

I tried giving _all_ permissions to this user : project admin, team admin plus all process permissions. It did not help. I looked into roles and permissions for something like "associate" permission. But I am not successful. I found things like com.ibm.team.scm.ChangeSet, scm.MicroChangeSetActivity, com.ibm.team.scm.server.modifyChangeset. But I don't know if I can do something with it. Obviously I can not give JAzzAdmins permission for this requirement.

Ideas ?

== Context ==
I am trying to invent a way to code review snapshots. I.e. review all change sets found "between" 2 snapshots, and give a user a way to classify change sets into "accepted" and "rejected" groups. I thought of work item for doing so.

Jazz Foundation - Jazz Team Server 1.0.0.1
Rational Team Concert 2.0.0.1

0 votes



5 answers

Permanent link
I agree that a user should be able to associate any change set with a
work item that is writable by that user. This has been requested in
work item 57870. Please feel free to indicate your interest/support for
this functionality by adding a comment to that work item.

Cheers,
Geoff

On 10/5/2010 11:23 AM, gtab wrote:
Hello.

A user can not associate a change set he does not own to a work item.
He gets an error :
Source Control Operation (failed)
Permission demied

Problem
Permission denied during "Source Control Operation"
The user "---" does not have enough permissions on
associate a Work Item to a change set owned by by an other user. The
role JazzAdmins is required to perform this operation.

# In an other pop up I get
The operation is not governed by process


I searched for help and ideas. Found
Unable
to associate work items with change sets and
Question
about change sets attached to multiple work items. But is seams
not to be my issue.

I can as a JazzAdmins user do this operation.

I tried giving _all_ permissions to this user : project admin, team
admin plus all process permissions. It did not help. I looked into
roles and permissions for something like "associate"
permission. But I am not successful. I found things like
com.ibm.team.scm.ChangeSet,
scm.MicroChangeSetActivity,
com.ibm.team.scm.server.modifyChangeset.
But I don't know if I can do something with it. Obviously I can not
give JAzzAdmins permission for this requirement.

Ideas ?

== Context ==
I am trying to invent a way to code review snapshots. I.e. review all
change sets found "between" 2 snapshots, and give a user a
way to classify change sets into "accepted" and
"rejected" groups. I thought of work item for doing so.

Jazz Foundation - Jazz Team Server 1.0.0.1
Rational Team Concert 2.0.0.1

0 votes


Permanent link
Hello.
Thanks for the pointer to 57870. It makes me think I didn't miss something obvious : no solution to this technical whish. Now, question remains : is my idea of "triaging" change sets through work item association, for code review purpose, good ? Ideas any one ?
Regards.
Gilles

I agree that a user should be able to associate any change set with a
work item that is writable by that user. This has been requested in
work item 57870. Please feel free to indicate your interest/support for
this functionality by adding a comment to that work item.

Cheers,
Geoff

0 votes


Permanent link
Hello.
Thanks for the pointer to 57870. It makes me think I didn't miss something obvious : no solution to this technical whish.
...


One thing puzzles me though. If a "JazzAdmin" user can do this operation, there must be an "if" somewhere testing this permission. What would be the test ? Couldn't I find the element or property tested on, and/or the operation the test is performed on ? Like maybe com.ibm.team.scm.server.modifyChangeset.

0 votes


Permanent link
WRT reviews, aren't the developers already associating their change-sets
with an appropriate work item? (And if they aren't, they should be :-).
And if so, you can just add a "code review" approval to that work
item, which will queue it up for code review.

Cheers,
Geoff

On 10/6/2010 2:37 AM, gtab wrote:
Hello.
Thanks for the pointer to
57870.
It makes me think I didn't miss something obvious : no solution to
this technical whish. Now, question remains : is my idea of
"triaging" change sets through work item association, for
code review purpose, good ? Ideas any one ?
Regards.
Gilles

gmclemmwrote:
I agree that a user should be able to associate any change set with a

work item that is writable by that user. This has been requested in

work item 57870. Please feel free to indicate your interest/support
for
this functionality by adding a comment to that work item.

Cheers,
Geoff

0 votes


Permanent link
Hi again.

To my understanding, adding a "code review" approval to a work item, will queue it up for code review all-right, but will halt it being delivered on an integration stream for example. And because my idea is that we should review snapshots only ( because this is the CM object actually delivered ) this feature did not came to my mind as a good candidate.

The other idea is that their may be many many delivery a day on a stream, and I can't imagine halting every single developer each time he/she has to deliver. I try to clearly split code review and delivery activities so the velocity of the later does not impact the former.

Does this snapshot code review approach as opposed to change set / work item seams kind of acceptable ? To me it comes as most intuitive way.

Thanks.
Gilles

WRT reviews, aren't the developers already associating their change-sets
with an appropriate work item? (And if they aren't, they should be :-).
And if so, you can just add a "code review" approval to that work
item, which will queue it up for code review.

Cheers,
Geoff

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 05 '10, 11:09 a.m.

Question was seen: 5,886 times

Last updated: Oct 05 '10, 11:09 a.m.

Confirmation Cancel Confirm