Request | Description | Desired behavior | Koidra response | Status | Severity | By | Submitted at | Attached files | |
---|---|---|---|---|---|---|---|---|---|
Metric selection filtering is already supported. Won’t fix. | Won't fix | ||||||||
Report: how much is the yield in week, month, year in tabular format | Already have it in our roadmap. The feature was developed and is being reviewed with end users. | Done | |||||||
We’ll fix this bug ASAP. The functions are already available in Opera. | Done | Critical (I can't use your product yet) | |||||||
The feature was released for cutomers. | Done | ||||||||
The feature was released for customers | Done | ||||||||
Missing the name of the person who edit the setpoint in single setpoint history | DONE | Done | |||||||
Comparisons are currently not feasible due to inconsistent metric names. The issue will be fixed in the end of June. | In progress | ||||||||
Whenever Opera operates, it operates all the setpoints even the setpoints that are under development. Temporarily, users have to delete the formulas of these setpoints. | This feature is definitely necessary, we added to our roadmap. It will be released in July. | In progress | |||||||
Quickly replicate a formula and change the variables inside the formula for other compartments | We introduce the feature group setpoint, this feature allow users to configure one formula for multiple compartments. It will be released in July. | In progress | |||||||
Limit the CO2 setpoint of autopoilot to 600 ppm. Set the minimum for the vent to 5% night and 10% during the day because the humidity is high. | We already supported to limit the CO2 setpoint. High humidity is a valid issue, however, we prefer to update the vent control logic rather than open vent at 5% night and 10% day. | In progress | |||||||
- Short-term: We will add any requested value
- Long-term: Make it more configurable by the users so the user can enable the data on KM by themselves | P1 | ||||||||
We will fix this issue ASAP | P1 | ||||||||
Need to clarify how this feature is used. | P2 | ||||||||
Need to clarify how this feature is used. | P2 | ||||||||
We already had it on our roadmap. Plus, we’ll move the Alias to the tab Automate as well. | P2 | ||||||||
We make it a P2 item because a zone (or phase) should have a single decision making grower who would set up the alerts for that zone. | P3 | ||||||||
This is nice to have; however it would require some nontrivial design thinking | Not started | ||||||||
Support calculation of the temperature or other metrics from sunrise to sunset
Check the bug as there is only data of calculated RTR available in the past 24 hours | Not started | ||||||||
WS will get back to us for their reference information and user stories on how they want to use these information | Not started | ||||||||
Math: can be done easily with linear regression.
UX: how to enable it? | Not started | ||||||||
We need to clarify other use cases. | Not started |