Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




v3.0.4: Gemini Administrator cannot add/remove user from Project Groups?

web-app

Is that correct?

My user name is in Gemini Administrator which has all the scheme roles (except View Only Own Issues).  Gemini Administrator group is Global Group.  It is added to existing project calls TEST AREA.
Instead of going to TEST AREA -> Project Administrator -> Project Group.  I went to Administrator link (next to  Home link), i clicked on Project Group -> It shows all the existing project groups.  There is only "delete" option available.  Conclusion: if you don't have Project Administer role in certain project, you cannot add/remove user for existing Project Group even you are Gemini Administrator.  This is somehow odd to me.

Another odd thing that i'm seeing:
With Project Administer role -> Go to that project -> click on Project Administration link -> click on Project Groups -> You are able to add/remove users in ALL (i mean all) the existing Project Groups. 

I created couple of different Project Groups: BRTRC, TEST AREA, ARCHIVE.  They are meant for separate projects (with the same name).  However, a Project Administrator of TEST AREA can edit BRTRC project group.  It seems like this doesn't function right.  Instead, Gemini Administrator (not project administrators) should be able to edit ALL existing Project Groups.

kha
· 1
kha
Replies (6)
helpful
0
not helpful

I do not think you understand the project groups concept in Gemini.

It allows you to delegate the security control to the project admins.

See our webcast on this: http://countersoft.com/webcasts/gemini/ProjectGroups/ProjectGroups.html


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

How come in my Administrator link --> Projects Group, it has only Delete (but not edit)


kha
· 1
kha
helpful
0
not helpful

I think i understand Project Group concepts of Gemini correctly.  It allows you to add members who involved in that project.  For example, i have project called TEST AREA, I then created project group names Test Area, then add 4 users (for say, Alen, David, Mary, Chris) to that Test Area project group.

I go to TEST AREA project, assign  project group Test Area with View Project scheme role.  That means all 4 members (Alen, David, Mary, Chris) in that Test Area project group can view TEST AREA project.

From viewing the video, I surely don't think I misunderstood the Project Group concept.  The problem is that I don't see Edit/Delete Action (but only Delete action) like in the video on Administrator->Project Groups page.  Consequently, I don't see this EDIT page like in the video (no Project drop down list)


kha
· 1
kha
helpful
0
not helpful

The edit feature has been added as part of 3.1.

However, what you are describing is global group.

Project group spans multiple projects so you might create  Developers project group that for some project, say X, Developer A will be assigned to and for another project, say Y, Developer B is assigned. They both belong to the same project group but can see and work on different projects.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I am not quite understand what you said between project X and Y.
If developer A and B belongs to for says "Developer" project group, how can developer A is assigned to project X (but developer B is not)?

What in my mind is as followings:
1) Create Project group names: Developers
2) Assign Developer A and developer B to Developers project group.
3) Assuming project X and project Y already created and existing
4) The only way to assign scheme role (for example: assignable to issues) to Developer A for project X is going to scheme (for says, X scheme), select Developers project group and select "assignable to issue", click Add button. 
5) Go to project X and add X scheme as security scheme
6) Result of step 4 and 5 will be: both developer A and developer B listed as resources of project X even though our initial intention is only assign developer A as resource of project X.

Are my understanding and my method of setting security scheme having something wrong?


kha
· 1
kha
helpful
0
not helpful

The only way to assign users to a project group is via the project you want them to see.

So you add Developer A to project X by adding him from that project to the Developers project group

And  you add Developer B to project Y by adding him from that project to the Developers project group

They both belong to the same PROJECT group by can not see each other's project.


Saar Cohen
· 5000
Saar Cohen