On a client database with a big filestore, the staging clone sits with no progress for a long time. I cannot tell if it is still copying or if it has failed. A short status line would help.
Public board
Tell Hamdek what to build next
Anyone can read the board. Sign in to post, comment, or back a note.
After a branch sync I can see success or failure, but not whether the build is getting slower. A duration on the deployment row would make that obvious before a client asks why staging feels late.
Opening Odoo as a specific user from the project page removed a lot of "can you try logging in as them" messages. That is the part I would not want to lose.
If I leave the shell tab and come back from another project, the session is gone and I have to reconnect. Keeping it alive a little longer, or showing that it expired, would save a few minutes each time.
Backups are only useful if we know a restore works. A way to restore last night's backup onto staging, without touching production, would make the monthly check much calmer.