It's all about the answers!

Ask a question

Unable to change the File Against Attribute


Sunita Dinakar (11413742) | asked Feb 07 '11, 6:48 a.m.
Hi,

We currently have a configuration such that a person with a role "X" can only modify the due date attribute. When a user who has a "Team Member" access tries to modify the "Filed Against" attribute, he gets a permission denied error message while saving the work item with an error like the below.


In order to carry out this operation, you would need permission to perform the following additional actions:
Action: ID:
Modify the 'Due Date' ...


Later, trying to figure out if there were any mistakes in the configuration, we realized that the error is reported for a team member while modifying any of the date type fields.

Are we missing anything?

2 answers



permanent link
Ralph Schoon (63.1k33646) | answered Feb 08 '11, 3:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Sunita,

I can't tell from your description below what the issue is. It could have to do something with inheritance. Did you check team members have the permission to change the due date in the team areas and the project area? The permission is tied to the are that owns the work item. Changing filed against moves it into a different team and the permissions are controlled by that team.

Have you checked this article http://jazz.net/library/article/291 for details on how the permission lookup works?

In addition in the Eclipse client on the team artifacts view, you can click on a project and run "Generate Runtime Report" to get a better understanding on the roles of team members.

Thanks,

Ralph

Hi,

We currently have a configuration such that a person with a role "X" can only modify the due date attribute. When a user who has a "Team Member" access tries to modify the "Filed Against" attribute, he gets a permission denied error message while saving the work item with an error like the below.


In order to carry out this operation, you would need permission to perform the following additional actions:
Action: ID:
Modify the 'Due Date' ...


Later, trying to figure out if there were any mistakes in the configuration, we realized that the error is reported for a team member while modifying any of the date type fields.

Are we missing anything?

permanent link
Sunita Dinakar (11413742) | answered Feb 08 '11, 3:45 a.m.
Hi Ralph,

Thank you for the response.

We do not want the users with "Team Member" role to modify the due date. I have checked under the team area process customization as well. The problem is, Filed Against can be modified by both the roles in the team area and project area as well. So why is this causing an issue?


Hi Sunita,

I can't tell from your description below what the issue is. It could have to do something with inheritance. Did you check team members have the permission to change the due date in the team areas and the project area? The permission is tied to the are that owns the work item. Changing filed against moves it into a different team and the permissions are controlled by that team.

Have you checked this article http://jazz.net/library/article/291 for details on how the permission lookup works?

In addition in the Eclipse client on the team artifacts view, you can click on a project and run "Generate Runtime Report" to get a better understanding on the roles of team members.

Thanks,

Ralph

Hi,

We currently have a configuration such that a person with a role "X" can only modify the due date attribute. When a user who has a "Team Member" access tries to modify the "Filed Against" attribute, he gets a permission denied error message while saving the work item with an error like the below.


In order to carry out this operation, you would need permission to perform the following additional actions:
Action: ID:
Modify the 'Due Date' ...


Later, trying to figure out if there were any mistakes in the configuration, we realized that the error is reported for a team member while modifying any of the date type fields.

Are we missing anything?

Your answer


Register or 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.