Closed MartinFijneman closed 1 month ago
to resolve:
Crash does not happen anymore, but Iteration 0 indeed appears. Needs further investigation to find the exact cause. Seems IME related, not server.
Server side we are able to edit elements of the "old" frozen Iteration and probably the return message of that one creates the white screen: No Elements contained by the old frozen iteration which is indeed the case from a database perspective. The server should not allow updates to frozen Iterations and its full containment tree.
Prerequisites
Description
iterations - create new iteration needs better handling in other clients
NOTE: general issue, do not expect this issue to be related to dotnet 6 version, but not yet completely investigated on reference version 9.3 posted now as general issue
Steps to Reproduce
multi-client test, client A to create new iterations, client B with domain expert participant to get in updates for new iteration
Logs
System Configuration