It's all about the answers!

Ask a question

Project area membership


Bill Higgins (4562523) | asked Jan 27 '08, 10:21 a.m.
JAZZ DEVELOPER
(Note: I'm a member of the Jazz development team, but while experimenting with my own server, I had a question, and in the spirit of transparency I ask it in the forums <g>).

On my local machine, I created a new repository, a new project area, and a new team area. I'm the only user of the repository at the moment and it wasn't clear to me whether I needed to make myself a member of the project area, the team area, or both.

I understand what you can do by assigning users to team areas and assigning roles to users in the context of a team area, but the implications of making a user a member of a project area weren't clear.

So the question: When should a user be a member of a project area, and what capabilities/permissions does this give the user vs. just being a member of one of the child team areas?

--
Bill Higgins
Jazz Web UI Foundation Team

2 answers



permanent link
Bill Higgins (4562523) | answered Jan 29 '08, 9:35 p.m.
JAZZ DEVELOPER
Ah, this makes sense. I always wondered what special permissions Erich had that allowed him to modify work item categories while I was forbidden - the answer is that he's got the right role in the Jazz Project project area itself, whereas I'm not even a member of the project area itself (I'm a member of several child Team Areas).

Glad I asked! Thanks Jared.

--
Bill Higgins
Jazz Web UI Foundation Team

permanent link
Jared Burns (4.5k29) | answered Jan 28 '08, 12:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Assigning a user a role on the project area allows you to configure
role-based permissions for project operations.

Project operations are operations who scope is the entire project - for
example, saving the project area itself or saving the project's work
item categories.

You can see this in action on jazzdev. The Jazz project area is
configured such that only people with certain roles (like PMC or
projectadmin) can save the project area. In order to grant a user
permission to modify the project area, they're given a role assignment
at the project area level.

bill wrote:
(Note: I'm a member of the Jazz development team, but while
experimenting with my own server, I had a question, and in the spirit
of transparency I ask it in the forums <g>).

On my local machine, I created a new repository, a new project area,
and a new team area. I'm the only user of the repository at the
moment and it wasn't clear to me whether I needed to make myself a
member of the project area, the team area, or both.

I understand what you can do by assigning users to team areas and
assigning roles to users in the context of a team area, but the
implications of making a user a member of a project area weren't
clear.

So the question: When should a user be a member of a project area, and
what capabilities/permissions does this give the user vs. just being a
member of one of the child team areas?

--
Bill Higgins
Jazz Web UI Foundation Team



--
Jared Burns
Jazz Process Team

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.