This is an issue that was introduced by changing list of "Products" to "Products or Component".
We realized it is source of issues and mess.
So there will be a change in V5.3 to get back to previous system, and ass list of components beside list of products (not in the same list).
To revert to old system befote V5.3 is deployed, just remane field "idProductOrComponent" to "idProduct" in /model/Ticket.php.

Just to be a nuisance... 👿
I actually like the fact that only some Products can be selected from a given Ticket !

It's especially necessary when we have multiple customers who access our Projeqtor instance to create support requests for example: for confidentiality reasons, we do not want Customer A to be able to see products which belong to the project of Customer B...

Ideally (for me at least) :
- By default, only Products linked to a given project are visible in drop-down lists
- We can have an option (checkbox) on Product if we want it "always visible"
- I would even have a direct link Product - Project, even if the Product does not use versions

Depends on whether that behaviour is interesting for others of course 🙂

Hello Babynus,
Your advice doesn t not work.
Is there a chance to come back and to have the whole list of products?
Thanks

Hi,
Maybe advise is not good because I did not understand your problem at first.
If I can summarize, you expect on tickets to have list of products including all tickets, without any restriction.
The fact is there is a restriction that was introduced in V4.4 to limit list of products to products linked to project through version (Ticket #1457).
My misunderstanding come from the fact that this change is quite old...
... and sorry but there is not chance to revert to old behavior in standard version as it seems to fit most users needs.

It you with to revert, you'll have to :
- define new objet, extending Product, with different name (for instance OwnProduct).
- hide Product on ticket screen
- add field idOwnProduct on Ticket.
If you wish to have this done for you, just request for a quote, we could do this for you as a plugin.

Hello,
Yes it is a quite old topic. I came back to this because several users in my company were unhappy with the current functionality.
I think it is not worth to develop a plugin if other users have not the same need.
Thanks.

I think it is not worth to develop a plugin if other users have not the same need.

My proposale was to develop a plugin for your own need, not for the community 😉