v1.2 — Known issues and temporary Full Update recommendation

[TMailletFR]

Known issues identified after the v1.2 release

Following additional real-world testing, several regressions have been identified in ProjectEngine v1.2.

The most important known issue concerns the incremental Update Gantt workflow. Some changes to predecessor relationships—particularly removing a predecessor or changing its relationship type—may not be fully detected. This can leave scheduling logic or displayed dependency links temporarily out of date.

Until the corrective release is available, users are advised to run Full Update after:

adding, removing or modifying predecessor relationships;
changing relationship types or lag values;
resizing the columns located to the left of the Gantt timeline;
observing a dependency link that appears inconsistent with the current schedule.

Additional investigations are in progress regarding:

SS and FF relationships using summary tasks as predecessors;
SVG dependency alignment and arrow visibility;
Longest Path REX results in schedules without Actual or Forecast dates.

A dedicated v1.2.5 stabilization release is being prepared to address these issues. Its scope is limited to corrective work and regression testing; no new performance or architectural development will be introduced.

The current v1.2 release remains available, but Full Update should be preferred over incremental Update whenever schedule logic has been modified.

Thank you to the users currently testing the release. Further details will be published with v1.2.5 once the corrections have been validated.

[TMailletFR]

Thanks for the offer. The repository is public, so you are welcome to run it through JigsawML and share the resulting architecture visualization.

I would be interested to see how well it handles a fairly large Excel/VBA codebase, particularly relationships between standard modules, class modules, UserForms, worksheet events and the scheduling workflow.

There are also dependencies that are not always expressed through straightforward function calls, so it would be useful to see which relationships JigsawML can detect and where its limits are.

Please feel free to share the demo here or send me a link when it is ready. I’d be happy to give you honest feedback on whether it helps with understanding regression impact in this kind of project.

[TMailletFR]

Thanks for preparing the walkthrough. The visualization is clear, and I can see how it may help someone unfamiliar with the codebase understand the main architectural areas and their relationships.

The analysis categories around bugs, testing gaps, performance and coupling also look potentially interesting.

One point I could not determine from the video is which exact repository state was analyzed. ProjectEngine has several public releases and the code has changed significantly between v1.2, v1.2.5 and the current main branch.

Could you confirm the branch and commit SHA used for the scan?

That distinction is important here, because some of the dependency and incremental-update issues described in the original discussion were already corrected in later revisions. It would also help me assess whether the reported findings refer to the current codebase or to an older release.

For my own workflow, I already use tools that have access to both the current code and its history, so the architectural overview is less essential for me personally. However, I can see value for onboarding or for giving an external reviewer a faster high-level understanding of a large VBA project.

I would be particularly interested in any concrete finding that JigsawML believes is still actionable on the exact commit analyzed, especially if it can point to the relevant modules or call paths.