It's all about the answers!

Ask a question

How to manage own work across two isolated project areas


David Csikkel (1313516) | asked May 14 '09, 4:46 a.m.
Hello,

this is description of our situation:
2 teams (team 1, team 2)
2 projects (project A, project B)
needs:
project A accessible only by team 1
project B accessible by both teams

Because access control is available only on the project area level,
we created two isolated project areas according to projects and
members of of project area A are only users from team 1 and
members of project area B are users from both teams.

Data isolation works well.

But how can I manage my work in comfortable way,
when I am member of both project areas and
much functionality is able to work only for one selected project area?
For example "one-project-area" functions are My work, work items quick search, queries.

I can see three possible solutions:

A. New function: option to select more project areas in "one-project-area" functions (two isolated project areas)

B. New function: the data isolation on the level of team areas (one project area, two isolated teams)

C. New function: the project area and sub-project area hiearchy (one project area, two isolated sub-project areas)

Which one should I use for the request of a new feature?

BR
David Csikkel
Process consultant - Tieto
Ostrava - Czech republic

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered May 14 '09, 10:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest "B".
There already is a request for most of A ("cross project queries"). The
problem with request A is that different projects can have differently
customized work item schema, which means queries in one project might
not make sense against another. But in your case, you don't need
separate work item customizations ... you just need finer-grained
control of visibility. So if you weren't forced to use two different
project areas, there wouldn't be a multi-schema query problem.

C is effectively just "B" with different terminology.

Cheers,
Geoff

David.Csikkel wrote:
Hello,

this is description of our situation:
2 teams (team 1, team 2)
2 projects (project A, project B)
needs:
project A accessible only by team 1
project B accessible by both teams

Because access control is available only on the project area level,
we created two isolated project areas according to projects and
members of of project area A are only users from team 1 and
members of project area B are users from both teams.

Data isolation works well.

But how can I manage my work in comfortable way,
when I am member of both project areas and
much functionality is able to work only for one selected project
area?
For example "one-project-area" functions are My work, work
items quick search, queries.

I can see three possible solutions:

A. New function: option to select more project areas in
"one-project-area" functions (two isolated project areas)

B. New function: the data isolation on the level of team areas (one
project area, two isolated teams)

C. New function: the project area and sub-project area hiearchy (one
project area, two isolated sub-project areas)

Which one should I use for the request of a new feature?

BR
David Csikkel
Proccess consultant - Tieto
Ostrava - Czech republic

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.