-
- Banner with error message describing the problem
- Notification button showing the latest error messages
- A "See all notifications" button which leads to an overview of all notifications
Link …
-
**Describe the new feature you would like to see**
It is required to limit access to robots and functionality based on the facility and the role of the person working on it.
**Describe the solutio…
-
**Describe the improvement you would like to see**
Each new mission run should be assigned an incremented integer.
**How will this change existing functionality?**
This needs to be done with a mu…
-
**Describe the bug**
Semaphores are being ignored since they are local to the current scoped service instance. Each time a different dependency injection is done, a new semaphore is created.
**To …
-
**Describe the bug**
The get-area endpoint throws an exception when adding any filter criteria.
**To Reproduce**
Just run as usual and try out the get areas endpoint with filter criteria.
**Expect…
-
**Describe the bug**
When the stop button is pressed, the text that is displayed says that the robot will be sent back to the charging station.
This is not true for , for example.
**To Reproduce**
S…
-
**Describe the new feature you would like to see**
On top of showing that a localisation mission has been run on the robot, we should also show which deck this was done on last.
**Describe the sol…
-
**Describe the test you would like to make**
Write a test, which matches the Role based granular access (Role.Installation.User or Admin) with the current chosen installation (the installation sent a…
-
**Describe the improvement you would like to see**
We currently store whether the mission queue for the robot is frozen, but do not reflect this in its status.
**How will this change existing func…
-
**Describe the improvement you would like to see**
At the moment we only do console logging in the frontend. We should change this to a logger so the logs can be sent to application insights and be s…