View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Supportez nous sur Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - [10.4.5] wbs, plannigelement wrong - ProjeQtOr

Prochaines sessions de formation

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

 

Démonstration de ProjeQtOr

(gratuit, sur inscription)

Mardi 23 avril (10h30-12h)

Jeudi 16 mai (16h-17h30)

Jeudi 13 juin (10h30-12h)

 
 

Planifiez avec ProjeQtOr

3 et 4 avril (9h - 12h30)

 
 

Administrez avec ProjeQtOr

10 et 11 avril (9h - 12h30)

 

 

 
 

[10.4.5] wbs, plannigelement wrong

More
25 Sep 2023 15:13 - 25 Sep 2023 15:14 #1 by ddal
after upgrading from 10.3.5 to 10.4.5. The cron that is calculating wbs for projects and planningelement is behaving wrong.

in the changes log there are rows like this:
data value before value after date user
update wbs 414 416 23/09/2023 01:06:26
update wbs 414 416 23/09/2023 01:06:06
update wbs 414 416 23/09/2023 01:05:41
update wbs 414 416 23/09/2023 01:05:17
update wbs 414 416 23/09/2023 01:04:56
update wbs 414 416 23/09/2023 01:04:37
update wbs 414 416 23/09/2023 01:04:17
update wbs 414 416 23/09/2023 01:03:52

but the main project in planningelement has different wbs and wbssortable from the project itself. But it calculates the activities under it with the correct wbs. So the planning view is then broken. The elements are not under the project but next to it.
Last edit: 25 Sep 2023 15:14 by ddal.

Please Connexion or Create an account to join the conversation.

More
26 Sep 2023 13:34 #2 by ddal
There is something seriously wrong with the calculations. I think it is caused by the 10.4.0 wbs change. It tries to fill in the gaps. As in before the sortOrder was 00301 and the next one was 00303. The new version changed 00303 to 00302 to fill in the gap. But then in planningelement it did not fix the project wbs. It changed the wbs on activities but did not change the project wbs.

Please Connexion or Create an account to join the conversation.

More
27 Sep 2023 09:24 #3 by ddal
Manually running the consistency checks from administration seem to have helped for now. Even though I don't understand why that helped, when the cron should be running them automatically at 1am, and from the logs it is clearly running something at 1am.

Please Connexion or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.031 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.