We do not reproduce.
Can you repeat these manipulations on our site demo.projeqtor.com?
 

Hi,
I did the following tests on your "Demo" site, from the "Gestionnaire" account. I did not make any modification or creation, no new project, nor new product.

There are 2 products:
- "swing..." on the Test2 project
- "web ..." on the TestMEGADEMO1 project

Select "All Projects"
Go to Ticket and create a new Ticket.

The default project is "project one". It is not a sub-project of those having a product. The product list displays "web..." instead of being empty. Why?

Change the project with "fertilization". It is not a sub-project of those having a product. The product list shows "web..." and "swing..." instead of being empty. Why?

With other projects, the list is empty, and with the "test2" and "TestMEGADEMO1" projects, we find the respective product of the project.

I don't know if it's the same problem as originally described, but the behaviour doesn't seem consistent with the expected.

It is difficult to compare with your Demo, because there are so many configuration parameters that can be different. Hence my question about perhaps parameters to check.

Then I did other tests with our Projeqtor instance.

I added my "Customer" resource on another P2 project with defined products.

I create a Ticket on the P1 project, I still have my problem, the list of products contains all the products of all the projects.

I create a Ticket on the P2 project, the list of products only contains the list of P2 products. So like what I expect.
Without saving, I change the project to P1.
This time the product list is empty.

I save my ticket with the Product choice set to "empty".

I open the list of products, I find all the products, ie my initial problem.

The default project is "project one". It is not a sub-project of those having a product. The product list displays "web..." instead of being empty. Why?

Because project "Project One" is linked to Product Version "Web Application V2.0".
Note that the relationship taken into account for lists is Project - Product Version.
The relation Project - Product is just a shortcut to automatic link all versions of the product to the project.
This has a drawback : products without versions are not managed as you may expect.
This can be the source of your issues.

Hello,

yes, I understood that mechanism.
But if I go back to my initial example, I did not understand why my Admin profile had a list restricted to the project, while my customer profile had a list with all the products of all my projects.

Following your last remark, I made checks. And I noticed that in my example, the products were declared in the parent project, while the Customer was a resource in the child project.

I did a test by directly adding the products also to the child project, and in this case, when creating a Ticket, the list of products is limited to those of the project.

Normal or abnormal, you tell me.

Thanks again

Change the project with "fertilization". It is not a sub-project of those having a product. The product list shows "web..." and "swing..." instead of being empty. Why?

Project "fertilization" is linked to Prodcut Version "swing application V1.0", and it is sub-project of "Project One Maintenance" (that is also linked to "swing application V1.0", which is sub-project of Project One "Project One" that is linked to Product Version "Web Application V2.0". So, with inhéritance, fertilization is linked to Products "swing application" ands "Web Application"

Hi,

I recreated your use case and could see some unecpected list : list of projects is "full" althout list of versions is correctly restricted to versions linked to parent project