Forum SquashTM

Hi, Some answers: - Does the Gitlab search on the same perimeter as your simulation return the same number of tickets (i.e. 182)? --> No, it does not. The simulation mentions a lower number than present in GitLab (with the same filters applied) - Did the synchronisation immediately 'Fail' following ...

I've also trie recreating the synchronization in a sandbox project. Same server, same settings but no equivalences set.
Simulation is successful, see image. Synchronization itself fails with same reason and logging as before.
André

Hello Xavier, The GitLab used is GitLab CE (Community Edition) version 15.10. We do use 'equivalences'. The first part is captured in the image attached, the second part is: status: In review: under_review Requirement change pending: under_review In progress: work_in_progress Done: approved Rejected...

Hi Xavier, I did upgrade all plugins as well indeed and the log file attached was the logfile from the new synchronization supervision page (which I do like very much by the way). The synchronization status for the already synced requirements is red for the root folder and black for all requirements...

I've been using Squash Community edition for several months and recently updated to v6. I also have a GitLab repo from which I have been synchronizing issues succesfully until a week ago. For some unclear reason, the synchronization is now failing with this error on top: org.hibernate.AssertionFailu...