Hi,
Yes, with so many projects, the list will be truncated.
By the way, only admin user will face this issue.
Other users will have the list restricted to the affected projects.

I will try and find a fixing / workaround, without any garanty...

Regards

Hi,

thanks a lot for development of the project selector , very useful

but i have a little problem in version 1.9.0 , i don't know if a bug or if a configuration is missing

With external account (member or manager) , i can't see list of affected project i see only 'all project' in project selector

The problem appears on an account which have an acces on one project with 5 sub-project

Could you help me to solve this issue ?

P.S: i used the same topic , if you prefer i can create a new one

Hi,

thanks a lot for development of the project selector , very useful

but i have a little problem in version 1.9.0 , i don't know if a bug or if a configuration is missing

With external account (member or manager) , i can't see list of affected project i see only 'all project' in project selector

The problem appears on an account which have an acces on one project with 5 sub-project

Could you help me to solve this issue ?

P.S: i used the same topic , if you prefer i can create a new one

Could you send me some print screens of user / afeectation / selector ?

hi,

for screenshot I have sent you a message

moreover I continued to move forward on this issue.

I have several external sub project attached to a main project , I configured oria by following this principle, Works fine in v1.5.5

Main project --> internal ressources
**Main sub project external --> user external 1 , user external 2 , user external 3
*** sub project external 1 --> user external 1 , user external 2
sub project external 2 --> user external 1 , user external 3
*** sub project external 3 --> user external 1 , user external 2 , user external 3

doesn't work in v1.9.0 , it seems project selector filter only root project affectation , external users don't see the sub projects

Hi;,
I received your mail, but cannot get the screenshot : a user/password is required.

Hi babynus,

login must be empty and pasword is &prjselect%

thank you
Best regards

Hi,
I downloaded the screenshots.
I'll have a look.

Hi,
I finaly found the time to analyse your screen shots.

First, I tried to reproduce, but could not : with exactly same parameters, I had a correct list.

In your screenshots, I found somethong strange :
- in user, the "anoury" reosurce is also a user
- in affectation list, "anoury" is displayed as a resource, but not as a user.
This looks like an issue from V1.7 and V1.8, fixed in V1.9.
You can just try and select the affectations, and just save, without any change.
If my guess is correct, you should have message "affectation saved", even if you made no change.
Do this for all the affectations.
Then test again.

I hope this will fix your issue.

Let me know the result.

Regards.

Hi babynus,

this problem is effectively solved when the assignment contains the name of the user and the resource, being given the number of assignment or there is the problem, I will prepare a request to perform update directly to the database.

thank you for your help