You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the improvement you would like to see
Implement a description for a mission plan. The description should be given by the user making the plan in the first place and should ideally contain information about the purpose of the mission and any analysis information required. This information should then be readable in the mission run overview.
Most likely this should be implemented in mission planner as a text box which the user is prompted to fill out when creating the mission.
How will this change existing functionality?
Improved understanding of operators of why a mission should be running and potentially what to look out for in case of anomalies detected in some analysis.
How will this improvement affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered:
Suggested implementation in Echo:
The easiest solution is to add another field when creating/editing a mission plan which is a text box called "Description". This takes whatever text the user decides to add and is attached to the mission plan object. Whenever a request for a mission plan is made in the API the description is also attached to the result.
Value:
This is a requested feature from the operators in order to tie back what is the purposed of the robot mission. The user creating the missions knows this best and should be in charge of adding the information. By allowing editing it can also be updated later with more information or if the purpose has changed.
A few other things to note about comment/description
A missionRun has both a description and a comment. Should be enough with just one of them
When using custom mission endpoint to schedule a mission with a description and a comment, the corresponding missionRun will have a description visualized in missionPage, but the missionDefinition will not store those values.
The corresponding mission definition will have comment null and no description. If running the mission from missionDefinition, it will not have a description anymore
Describe the improvement you would like to see
Implement a description for a mission plan. The description should be given by the user making the plan in the first place and should ideally contain information about the purpose of the mission and any analysis information required. This information should then be readable in the mission run overview.
Most likely this should be implemented in mission planner as a text box which the user is prompted to fill out when creating the mission.
How will this change existing functionality?
Improved understanding of operators of why a mission should be running and potentially what to look out for in case of anomalies detected in some analysis.
How will this improvement affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered: