Hi,
I am asking for your help with a problem for which I am unable to identify the cause.
When linking a product to a project, I notice these unexpected behaviors :
- The project product version links, created automatically, are directly and systematically "closed".
- If I try to uncheck "closed" on these links, the system does not save any changes and the link remains "closed".
- The product is not offered in the "Product" list of the elements of this project (for example on the tickets), although this is the desired objective.
I see this for any project and product.
The affected products and product versions are not closed.
These issues are seen on ProjeQtOr V9.0.6, but I don't think the version or the app is to blame.
These actions do not produce an error in the logs.
In the past, it worked fine on this same basis.
I do not reproduce these behaviors on another test installation of ProjeQtOr, nor on demo.projeqtor.org.
What setting could be causing this problem ?
Could this be caused by an error in the database ? If yes, what to do ?
If not, what do you advise me to do to try to fix this ?
Thanks
Tony44
Hi,
It is not the links that are closed, it is the versions.
Thanks for the reply.
It is not the links that are closed, it is the versions.
Unfortunately no, the product versions are not closed :
When the product version is closed, the project version link is locked closed (the closed box is checked and grayed out) :
Here it is not the case, I can uncheck "closed" on the link project version, but when validating the system indicates that there is nothing to save and check the box again :
Do you have another idea ?
Tony44
I don't understand where is the issue.
You have close property on Version and on Project-Version relationship.
If Project-Version relationship is closed, you cannot use the version on the project.
if Version is closed, all its Project-Version relationship are also automatically closed.
Yes, I understood the expected behavior
The issue is that we cannot uncheck the close property on project-version relationship.
This for some unknown reason (the version is not closed)
Tony44
Strange.
I tried again and there is not issue to check / uncheck link.
Checkbox is readonly only when version is closed.
Maybe you can delete the link and re-create it.
Yes, strange.
babynus post=30127
I tried again and there is not issue to check / uncheck link.
Checkbox is readonly only when version is closed.
Of course, this is not a general anomaly of the application but specific to our database or configuration, see my 1st post :
I do not reproduce these behaviors on another test installation of ProjeQtOr, nor on demo.projeqtor.org.
babynus post=30127
Maybe you can delete the link and re-create it.
Remove link is useless: the box is automatically checked for all new links, including a new version and a new project.
Can this be caused by an error in the database ?
Thanks for your help
Tony44
Just re-reading the full post, I noticed the Version used (1-0) is closed.
This may explain the behavior
No problem for closed versions, for which the project-version relationship is necessarily closed.
The issue is for unclosed versions.
It occurs for all versions of all products and on all projects.
Example:
- I am creating a new project.
- I am creating a new product.
- I am creating a new version on this product.
- I associate the product with the project.
- The project-version relationship is immediately closed by the system.
- It is not possible to reopen the project-version relationship.
Can this be caused by an error in the database ?
Tony44
I don't know what can cause this behavior as I do not reproduce.
I just tried use case on demo, and all works fine.
You can have a look on demo (connect as manager) on project 'PROJECT'.
Can you please try and reproduce your use case on demo ?
Indeed, the issue cannot be reproduced on demo.projeqtor.org, as I indicated in my 1st post :
I do not reproduce these behaviors on another test installation of ProjeQtOr, nor on demo.projeqtor.org.
The problem is specific to our database, that's why I suspect an error in the database.
What can I provide to help identify the source of the problem?
Thank you again for your help
Tony44
Hi,
Only solution would be to send us a dump (possibly anonymized) of your DB, for us to analyse.
But this is out of scope of free community support.
Ok I understand, thanks
Tony44
Hi,
Luky you !
I found the issue.
Will be fixed in V9.1.3
Hi,
Very good news 
Did you finally reproduce the issue ?
Thanks for the information
Tony44