Hello,

Please post your question in english.

It's the only one rules on the forum.

Thanks.

Hi, sorry about that

Here is my 'problem'. I'm using projeqtor 6.2

I've got a product which has several versions. It's linked to several components which also have several versions.

So product 'X' 'versions'> component 'Y' 'versions' > composed component 'Z' 'versions'

All versions has a reel start date. The versions that are not used anymore have a reel 'end' date (closed) .
I have closely linked the good 'Y' version to the 'Z' versions I wanted.
I also closely linked the X versions of the product to the good 'Y' versions of the components.

So I've got only 1 versions "in used" of the product at a time, all the 'old versions' are stated as closed

The problem is when create a project and I link it to the product 'X'

In the project sheet, it appears the product 'X' .. but also all the versions of the X product, even the closed one and all this without grabbing those versions start/closed date already filled in the "product version" specific tab...

I thought the 'project tab' will grab all the information from the product version ???

Is there a way to make the project follow the linked product life and bring back start / end (closed) date of that product ?

Will I have to enter again all the date of all the versions of the 'X' product, knowing that it can conflict with the date filled in the 'product version' tab ?

Please find attachment to see exactly what's i'm try to explain (h

even if it's french frontpanel, you will understand 😉

Thx for your answer and sorry for my english

I've made another test

I've removed the end time of an 'old' product version, so that i gain access to the start/stop/closed status of the project linked (in the product version tab)

From here, i can modify the start/stop/closed status ot the project linked to the version) and they appear in the project tab !
Ok I understand that a product can have a shorter livetime in a project, so you have to fill the at least start date of that version in the project ! (maybe stop date and closed status also)

However, as soon as i fill a end date of the version (so a closed status of this version), all dates filled in the linked project (start/stop/closed) dissapear ! Why ?.

For my point of view, when you close a product version, the end time of the product version should be written in the end time of the project linked (if it's not written yet) and in a closed status ,

so that THIS version of product (which is closed now) has been part of the project from date X to max date "end date of this version of product" and can't be further on as the version is closed ...

Where am I wrong in my thinking ? and abvioulsy, why I 've lost the project date of that product version when I fill in the end date of that product version... ?

Here is my 'problem'. I'm using projeqtor 6.2

Please share it with us !!!!
The latest I know is the V6.1.0 😉

The problem is when create a project and I link it to the product 'X'
In the project sheet, it appears the product 'X' .. but also all the versions of the X product, even the closed one and all this without grabbing those versions start/closed date already filled in the "product version" specific tab...

It is designed this way : when you link a product to a project, it means you lonk "all versions" without exception. If you want to link only one version, just link the version and not not the product.

I thought the 'project tab' will grab all the information from the product version ???

No, it was not required this way when designed.

Is there a way to make the project follow the linked product life and bring back start / end (closed) date of that product ?

No, not as of today, and no evolution is planned this way.

Will I have to enter again all the date of all the versions of the 'X' product, knowing that it can conflict with the date filled in the 'product version' tab ?

I'm afraid yes.
We could implement changes to fit your needs, to improve this behavior, but will not do it until it is sponsored.
So if you are interested, we may estimate the work to do it, from specification from your side.
Contact us through the contact form if you are interested.

However, as soon as i fill a end date of the version (so a closed status of this version), all dates filled in the linked project (start/stop/closed) dissapear ! Why ?.

There is no automatism to work this way.
So I think it may be due to other side, possibly planning calculation?

There is no automatism to maage project dates from version dates or reverse bahavior.

However, as soon as i fill a end date of the version (so a closed status of this version), all dates filled in the linked project (start/stop/closed) dissapear ! Why ?.

There is no automatism to work this way.
So I think it may be due to other side, possibly planning calculation?
There is no automatism to maage project dates from version dates or reverse bahavior.

Well i didn't have any planning for that project atm. I just wanted to prepare the project with past product version history.
But as I said as soon as I put an end date to the product version, the date into the linked project just erased... :/

hum...

Gonna try to update to last stable version .. (sure you understodd I was using 6.0.2 version 😉

I've updated Projeqtor to V6.1.0

Same result

See attachment to see what I'm talking about...

product_version tab with project section START/STOP/CLOSED ok but with no END DATE for product_version > This appears as expected into "project tab >all versions product section"

as soon as I closed the product_version in the product_version tab, the "product_version tab > project section" is cleared, and so is the "project tab > all versions product section"

OK, I better understand now....

First there may be a misunderstanding : on the productveriosn / project relationship, start and end dates have no link to version dates.
These are the dates of the validity of the relationship (it was designed this way to temporally fix duration of the relationship but theses dates are not used)

Then, the changes you face are due to link from Project to Product. This link just defines a relationship that will generate relationship for all versions of the product.
So dates for relation between Project and Product are copied to Product Version / Project relationship....
There way be an issue as these dates are not propagated on creation of the relation, but when updating product version...

We'll record a ticket to see what can be done to improve this behavior :
- remove start-end dates (as they have no major interest as of today)
- propagate project-product relation dates every time (fix missing behavior)
- never propagate project-product dates (except maybe on creation) to remove this maybe uexpected behavior.

Edit : Ticket #2559 recorded

OK, I better understand now....

First there may be a misunderstanding : on the productveriosn / project relationship, start and end dates have no link to version dates.
These are the dates of the validity of the relationship (it was designed this way to temporally fix duration of the relationship but theses dates are not used)

Then, the changes you face are due to link from Project to Product. This link just defines a relationship that will generate relationship for all versions of the product.
So dates for relation between Project and Product are copied to Product Version / Project relationship....
There way be an issue as these dates are not propagated on creation of the relation, but when updating product version...

We'll record a ticket to see what can be done to improve this behavior :
- remove start-end dates (as they have no major interest as of today)
- propagate project-product relation dates every time (fix missing behavior)
- never propagate project-product dates (except maybe on creation) to remove this maybe uexpected behavior.

Edit : Ticket #2559 recorded

Thx for your reactive action. Yes, obviously it's important to keep history of project/product version relationship 🙂
If I understood what you said, those relationships could be in the 'near future' only "editable" and visible 'only' on the project tab, where all version of the product are listed and when the relationship is declared ? That should be great.

However and just in my opinion, I find it also very confortable to have a "reminder" of the projet / product version relationship on the product version tab, even if it should be only readable and could be only modified on the project tab, you will directly see that this product version was (or is still in) used but this, this or this project from X to Y date.

Will this specific project/product relationship be 'warned' or "closed" at the project level when the specific product version has an ENDED date or CLOSED ?

If I understood what you said, those relationships could be in the 'near future' only "editable" and visible 'only' on the project tab, where all version of the product are listed and when the relationship is declared ?

Not in the near future, it alredy rexists. But will not be the only way. Project-Version relationship will still exist.

Will this specific project/product relationship be 'warned' or "closed" at the project level when the specific product version has an ENDED date or CLOSED ?

No, as relationshi^p may be still valid for existing or future versions.