You need to re-setup the security. This is because the security model has changed completely in 3.0.

See the migration guide: http://countersoft.com/downloads/csfiles/CounterSoftGeminiv300_Documentation.zip

I'm confused.

Do I see it right, that a security scheme can be different for different user groups?

Shouldn t the security scheme be always the same regardless for which group?

Currently I can selecte the unique permissions and set the to the global groups.

Sample:

Global Group:

1. Supporter

2. Tester

Security Scheme:

Name: Issue Worker

Permissions: Edit Issue, Delete Issue: Global Groups: Supporter

Permissions: View Issue: Add Comment: Globla Groups: Tester

In the sample above. The security scheme so called: Issue worker is different for Testers and for Supporters.

Thats confusing and very hard to manage when having multiple teams and schemes.

Deniz,

A security scheme defines who can do what on a project or projects.

You have different people, teams working on a project, right?  So you need one view, one place where you can see who can do what.

You just need to place the right people into the right Global Groups.  You then assign permissions to Global Groups via a Scheme.

Moreover, you define as few Global Groups and Secrutiy Schemes as possible: re-use.

What is confusing?

Thanks for the feedback.

There is a check box: System Group when adding a Global Group. What is the meaning of this and when should it be used?

System groups cannot be deleted.  That's it.