Currently, when a manager closes an iteration and creates a new one, team members need to manually refresh their browser to see the change. This is not ideal when FlowInquiry is being used live in meetings, where multiple team members are viewing the application simultaneously.
Proposed Solution
-
When an iteration is closed, emit an SSE event.
-
If a new iteration is created as part of the action, include it in the payload.
-
Frontend subscribes via EventSource and updates UI automatically (no refresh)
Technical Notes (Backend – Spring Boot)
Currently, when a manager closes an iteration and creates a new one, team members need to manually refresh their browser to see the change. This is not ideal when FlowInquiry is being used live in meetings, where multiple team members are viewing the application simultaneously.
Proposed Solution
When an iteration is closed, emit an SSE event.
If a new iteration is created as part of the action, include it in the payload.
Frontend subscribes via EventSource and updates UI automatically (no refresh)
Technical Notes (Backend – Spring Boot)