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

Filed Against and Custom Attributes

Questions
Tags
Users
Badges
Aaron Cabrera
(45●14●18) edited
Mar 06 '13, 2:14 p.m.
Recently, we added a custom field of type Tag to our Defect and Story editor pages called Release Label with id releaselabel.  A role called Release Manager was created and given the permission to modify the field.  No other roles were given the permission to modify it.

Now, when a user WITHOUT the Release Manager role changes the Filed Against field with out changing the Release Label field ... an error occurs

Problem:
You don't have permission to Save Work Item [server]

Reason:
In order to carry out this operation, you would need permission to perform the following additional actions:

Action:
Modify the 'Release Label' attribute

ID
modify/releaselabel

The user did not change the release label but gets the error when changing the Filed Against.  The user can change everything else and will not get the error.

Any ideas why this might be happening or how to troubleshoot the issue?

0 votes

3 answers
8,120 views
0 votes

3 answers

Permanent link
Lauren Hayward Schaefer
JAZZ DEVELOPER (3.3k●1●17●27) Mar 07 '13, 7:26 a.m.
Hi Aaron,
I'm not sure what could be causing this issue.  How did you setup the permissions to modify the field?  https://jazz.net/library/article/997/#dynwflow explains how to make a field read-only based on the role.

0 votes

Permanent link
sam detweiler
(12.5k●6●195●201) Mar 07 '13, 8:20 a.m.
Sounds like you have a script based Advisor which is posting an incorrect error message.

0 votes

Permanent link
Fred Atwater
(23●8●10) Jun 25 '13, 11:35 a.m.
We are experiencing the same problem. The way that it appears to work is:
When the Filed Against category is changed, the work item is moved to the new category, and the move appears to be implemented as a Cut and Paste, The Paste effectively creates a new instance of all attributes, and the user permissions do not allow the new custom attributes to be saved. I don't know the actual implementation, but I have seen this error with the cut and paste implementation elsewhere.
What we expect is that Filed Against is just another attribute that can be changed, but it has additional side effects.
We are preparing to submit an RFE to address this.

0 votes

Comments
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jun 25 '13, 12:51 p.m.
Changing the FiledAgainst property of a work item does not create a new instance of all attributes (and therefore is probably not an example of what you are calling Cut and Paste).  And yes, FiledAgainst is just another attribute that can be changed, with some side effects. 

Fred Atwater
Jun 25 '13, 12:57 p.m.
I used the cut and paste as an analogy. One side effect of changing the Filed Against value to a sub-category that is associated with a sub-team is to impact the other attributes of the work item in some way that I do not know, so that if the user does not have permission to modify any of them, saving the change fails. This happens with V4.0.1.

Fred Atwater
Aug 01 '13, 11:48 a.m.
 I finally received an answer from IBM Development on the PMR related to this issue: ******** <o:p> </o:p> Changing 'Filed against' is more than just an attribute change. It can also lead to a change in the process (team/project) area the work item belongs. <o:p> </o:p> To move a work item from one process area to another you need the same rights as when creating a new work item in the target area: <o:p> </o:p> - You need the 'modify' rights for each attribute which is not the default value I realize that our model is too restricted to be used the way you want it. <o:p> </o:p> So, this is not a bug, but as designed. To make our current model more powerful regarding team area change, we would need to look at this in a enhancement request. ******** 

Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Aug 01 '13, 5:37 p.m.
The current behavior probably does make sense.   Suppose you had permissions to do everything in a team area.  If this check against all property values was not done, you could just give a work item any properties you wanted, and then change the FiledAgainst to reassign it to a different team area where you do not have permission to set those values.

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.

Ask a question
Guidelines
FAQ
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
× 6,180

Question asked: Mar 06 '13, 2:06 p.m.

Question was seen: 8,120 times

Last updated: Aug 01 '13, 5:37 p.m.

Confirmation Cancel Confirm