-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display failure reason for failed steps #757
Comments
This is already in progress through this issue equinor/isar#457 The design choice changed a little so on hold while I'm travelling but will be continued afterwards. |
equinor/isar#457 has now been implemented and this issue may be addressed in the frontend. |
Suggest putting the error messages in the status column in the overview of the missions and adding a "Read more" button if the error message is longer than three lines. Link to figma sketches: https://www.figma.com/file/q6vsNRogzV6r9vTCCDsocd/Robot-Missions?type=design&node-id=4635%3A618997&mode=design&t=kfBOLaxRlmNfzIr3-1 |
It is also possible to update the map with a red color corresponding to statuses that have failed. But perhaps it will be a bit much and that it will be associated with danger, which is in most cases not true Link to figma: https://www.figma.com/file/q6vsNRogzV6r9vTCCDsocd/Robot-Missions?type=design&node-id=4637%3A632652&mode=design&t=b4SOdQXbJVojHvX7-1 |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
This issue has automatically been marked as stale as there has been no activity for 60 days. |
Describe the new feature you would like to see
ISAR, through equinor/isar#457, will start sending error messages for missions, tasks and steps during the progress of the mission. Through #871 these MQTT messages will be picked up and stored in the mission, task and step models.
Note the discussion in #871 where it might be that the error description should not be shown directly in the frontend, but rather a defined user facing message could be shown based on the error reason field.
Describe the solution you'd like
The end result of this issue should be that the error messages passed on from ISAR and stored by #871 are displayed in a meaningful way to the users.
How will this feature affect the current Threat Model?
Improved as users will be able to help debug the application and easily give feedback to developers.
The text was updated successfully, but these errors were encountered: