View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Supportez nous sur Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - [Milestone] - planned date - Page 2 - ProjeQtOr

Prochaines Sessions

Les prochaines formations et démonstrations sont ouvertes, inscrivez-vous rapidement !

 

Démonstration de ProjeQtOr

(gratuit, sur inscription)
 

13 mai 2025 (10h30-12h)

5 juin 2025 (16h-17h30)

 
 

Planifiez avec ProjeQtOr

14 et 15 mai 2025 (9h-12h30)

18 et 19 juin 2025 (9h-12h30)

 
 

Administrez avec ProjeQtOr

20 et 21 mai (9h-12h30)

25 et 26 juin (9h-12h30)

 

 

 

[Milestone] - planned date

More
02 Mar 2017 16:56 #7 by babynus
Replied by babynus on topic [Milestone] - planned date
Hi,

It is a problem for the 45° curve too. Because, it is not the real date which is displayed but the false planned date. It is a big issue about reporting for ou client.

I understand the mismatch.
In fact planned date is always last planned date when real is set. It has been set this way to keep in mind last planned date.
But now that baselines exist, this information may no longer be pertinent. So we'll have to think about 2 solutions :
- change 45° curve to take into account this situation
- change planned date calculation behavior so that it is set to real date when this last one is set. This solution seems better but cannot be included in a patch as it brings a major evolution in calculation, so could only be deployed in V6.2.

Also, concerning the 45° curve, when the real date is set before the planned date, the 45° cuve should be displayed the real date and not the planned date.

OK, we'll have a look.

Ticket #2590 recorded

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

More
03 Mar 2017 11:09 #8 by VERGES
Replied by VERGES on topic [Milestone] - planned date
It is a problem for the 45° curve too. Because, it is not the real date which is displayed but the false planned date. It is a big issue about reporting for ou client.
Hello,

I understand the mismatch.
In fact planned date is always last planned date when real is set. It has been set this way to keep in mind last planned date.
But now that baselines exist, this information may no longer be pertinent. So we'll have to think about 2 solutions :
- change 45° curve to take into account this situation
- change planned date calculation behavior so that it is set to real date when this last one is set. This solution seems better but cannot be included in a patch as it brings a major evolution in calculation, so could only be deployed in V6.2.

When do you planned to deliver the V6.2 ?

Also, concerning the 45° curve, when the real date is set before the planned date, the 45° cuve should be displayed the real date and not the planned date.

OK, we'll have a look.

This curves are shown to our customers. It is urgent to solve this issue ASAP.

Ticket #2590 recorded

Please Connexion or Create an account to join the conversation.

More
04 Mar 2017 18:59 #9 by babynus
Replied by babynus on topic [Milestone] - planned date
V6.2 is planned on April 17th.

We'll try and solve ticket #2590 with workaround on 45° chart on patch 6.1.2

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

More
06 Mar 2017 14:21 #10 by VERGES
Replied by VERGES on topic [Milestone] - planned date
Thanks you very much to consider our request,

Regards,

Pascal

Please Connexion or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.048 seconds

Paramétrages de cookies

×

Cookies fonctionnels

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Veuillez vous connecter pour voir vos activités!

Autres cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.