Skip to content
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

Provide context of module to robot, missions, and inspections #1011

Open
1 of 5 tasks
anetteu opened this issue Sep 18, 2023 · 6 comments
Open
1 of 5 tasks

Provide context of module to robot, missions, and inspections #1011

anetteu opened this issue Sep 18, 2023 · 6 comments
Assignees
Labels
backend Backend related functionality feature New feature or request frontend Frontend related functionality ux Issue needs input from UX designer

Comments

@anetteu
Copy link
Member

anetteu commented Sep 18, 2023

Describe the new feature you would like to see
When running a mission over a full deck with several modules, the detailed information of were the robot is and will travel is lost (unless you have very detailed knowledge of the inspection points). A suggestion could be to provide the context of a module to the robot, missions, and the inspection points. Should be discussed with ux designer, and maybe also with users.

Describe the solution you'd like
Some ideas for where this context could be provided:

  • Naming the maps. Unless you recognice the map, there is no way to see which map is currently displayed Improve frontend #1773
  • Adding a column with the module to the list of tasks on the mission page
  • Adding relevant modules on the mission overview
  • Adding current module on the robot card and/or mission card on the front page
  • Somehow displaying a map of the entire deck (but then maybe details are lost?)

How will this feature affect the current Threat Model?
Leave blank for maintainers to fill out if you are uncertain about this.

@anetteu anetteu added feature New feature or request backend Backend related functionality frontend Frontend related functionality ux Issue needs input from UX designer labels Sep 18, 2023
@anetteu anetteu changed the title Provide context of which module the robot is located at Provide context of module to robot, missions, and inspections Sep 18, 2023
@oysand
Copy link
Contributor

oysand commented Oct 16, 2023

On hold pending #950

@anetteu
Copy link
Member Author

anetteu commented Oct 29, 2023

Why is this issue pending #950? @oysand

@anetteu
Copy link
Member Author

anetteu commented Oct 30, 2023

Is it possible to do parts of this in the next release? For instance naming the maps to make it clear which map is displayed? @oysand

@aeshub
Copy link
Contributor

aeshub commented Dec 30, 2023

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Dec 30, 2023
@aeshub aeshub removed the stale This issue or pull request already exists label Jan 15, 2024
@aeshub
Copy link
Contributor

aeshub commented May 5, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label May 5, 2024
@aeshub aeshub removed the stale This issue or pull request already exists label Jun 14, 2024
@andchiind
Copy link
Contributor

andchiind commented Aug 12, 2024

Could we make this an epic and then make subtasks? Eg. add name to map, give location info to robot card, etc. I am moving it to New to create a discussion.

@Christdej Christdej added the epic label Aug 12, 2024
@tsundvoll tsundvoll removed the epic label Sep 30, 2024
@mrica-equinor mrica-equinor self-assigned this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality feature New feature or request frontend Frontend related functionality ux Issue needs input from UX designer
Projects
None yet
Development

No branches or pull requests

7 participants