Whenever a user makes an easy to track status change of webentities, it would be easy to propagate it immediately to the global status of the corpus displayed in the topbar and in the choice of stacks in inquiry overview, instead of waiting for the recurring get_status api call to answer (this could maybe also allow us to reduce the number of calls made to get_status)
We should at least consider :
[x] when a user changes status of the current webentity from the sidebar
[x] when a user changes a set of statuses from the list of entities in a stacj in "Inquiry overview"
[x] when a user changes a set of statuses from fast batch actions in the "Linked webentities" cartel
[x] experiment reducing the get_status refresh rate, for instance to 5s?
There is an issue when changing status from fast actions from linkedentities, it only increases the value of the new status without decreasing the other one
Whenever a user makes an easy to track status change of webentities, it would be easy to propagate it immediately to the global status of the corpus displayed in the topbar and in the choice of stacks in inquiry overview, instead of waiting for the recurring get_status api call to answer (this could maybe also allow us to reduce the number of calls made to get_status)
We should at least consider :