Usability suggestions for rollback between snapshots
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
### Description
If I create more than one snapshot of an instance, there are some usability issues I would like to point out:
1. There is no way to tell which snapshot is the current one for the instance or even the last one that was rolled back.
2. When I start a rollback, there is no visual feedback that something is happening. When I go to the Node-RED editor I see the message 'Lost connection to server'. I also get a 'timeout of 30000ms: exceeded' notification in the FlowForge interface but no indication what timed out? It doesn't appear this notification is important since the rollback still works. It takes over 2-3 minutes to do a rollback so I think some visual feedback would be useful. For instance, maybe show the log files?
3. In the audit log, it says I logged in to FlowForge after the rollback is finished. This seems like an odd message since I never logged out. There is also a message that 'Node-RED has stopped - something has gone wrong' which is not the case since it was a rollback.
A more minor point:
- there is an id below each snapshot. I am assuming this is an internal id but is it really needed in the UI?
### Epic/Story
_No response_
### Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Contributor guide
Assessment
This issue has not been assessed yet.