Make it possible to manually edit the end time of a status event
There are instances when the end time of a status event in Greenbyte is not correct.
For example, if a turbine is stopped and loses communication with Greenbyte. The end timestamp of the stop event will often appear in Greenbyte as the same timestamp that the communication outage was fixed. In reality, the stop event code may have occurred earlier than that (Greenbyte just didn't know, since communications weren't active).
The only fix today is for the user to contact Greenbyte support and request the change be made by them. This is inefficient and can be particularly cumbersome when working with large sites where there are multiple stop codes to correct.
It would be very helpful if the user could manually edit the end time of an event.
AdminJon Martin
(Customer Success Manager, Greenbyte)
shared this idea
We have great new features lined up that we can't wait to share with you. Unfortunately this request is not part of the roadmap.