Skip to content

Fix for not-found status not being displayed immediately in the request


This bug was caused due to the status being set only in the post load after the event has been persisted to the database. This means a second save needed to occur on this object after it had been persisted for the status to change.

This only affected the NotFoundEvent because all the others set the status on the request in their constructor.

However the constructor should not be the place to set a status on the Request object. We can instead just immediately apply the event to the Request when we add it and set the status correctly.

Closes #230 (closed)

Edited by Liam Clark

Merge request reports