Your request was rejected, because only team members are permitted to create tickets. We don't want users adding tickets without permission and cluttering our system.

As for your request it's already planned for after GJ becomes a part of CB 2.0 core. Photos will also get folders, commenting will be added, share links, like links, etc.. a lot planned that's not publicly announced as it's still early concept ideas.

Added new tickets to show some planned features.

Just a bit worry about migrating datas from GJ 2.5.3 / CB 1.8.2 to CB 2...

CB 2.x will be a migration and not an upgrade. We'll have migration scripts to migrate up to date CB 1.x releases to CB 2.x. Maybe not on initial release of CB 2.x beta, but we'll see. I can't really give specifics.

Maybe I also should not use at all the native "CB relations between" that exists ?

You can use the latest versions up to release of CB 2.0. I certainly wouldn't hold back your site for the sake of waiting for CB 2.0. While we have a goal of a Beta by end of year; it is planned to be an extremely basic beta to test core stability and will lack probably a lot of initial features as we add them gradually. GJ won't be in CB 2.x initial release, but after as I have to completely rewrite it with CB 2.x API and move it to the core.

Access level could be great for some usage, but I hope usergroups will be usable as well.
If not, well, I don't know how I could do...

Usergroups don't have a purpose in controlling views. That's not what they're for. Usergroups are for Permission controls and not access controls. With J2.5 you can create as many accesslevels you want with any combination of usergroups as you want so the possibilities are quite limitless. If you wanted it still usergroup based then you'd just create 1 accesslevel for each usergroup.

I actually assign a GJ group automatically based on a usergroup name.

That'll still work fine.

So the access level is based on Group Access (parameter from GJ).

It just means for the groups access instead of selecting Administrator for example you'd select Special.

If I had only the access level I could not be abble to affect this GJ group to J! goup.

Your usage should still work fine. Again, accesslevels can be added to J2.5 up to an unlimited amount. So you've no limitations. They're also dynamically assigned to users making them significantly more attractive for access control (as they are intended, usergroups is for permissions).

I guess it's a bit far to talk about that now, just to let you know how I use GJ actually.

I'll have a lot of work to do and will release a beta of course for feedback.