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

Overlay "View" table capabilities are inconsistent #7169

Closed
7 tasks
charlesh88 opened this issue Oct 23, 2023 · 1 comment
Closed
7 tasks

Overlay "View" table capabilities are inconsistent #7169

charlesh88 opened this issue Oct 23, 2023 · 1 comment
Labels
invalid duplicate or incorrectly filed type:bug
Milestone

Comments

@charlesh88
Copy link
Contributor

Summary

The telemetry table view provided in Open MCT's "View" overlay is inconsistent with capabilities available to the same view elsewhere, even for the same object. It appears as though we are using legacy code for that context which is different from the main table view.

Expected vs Current Behavior

Telemetry table view should have the same capabilities regardless of how it was invoked.

Steps to Reproduce

  1. Create or go to a view that uses the telemetry table view, like a numeric data source.
  2. In the main view, note the controls available and the contents of the More Options menu (3 dot menu) in the upper right.
  3. Nav away from the object, then find it in the tree. Context-click it there and select "View" from the context menu.
  4. Observe that available controls, and the contents of the More Options menu are different and very limited.

Full, desired table capabilities from the main view:
Screen Shot 2023-10-23 at 2 29 25 PM

Invoking "View" from the tree:
Screen Shot 2023-10-23 at 2 37 28 PM

The 2nd, limited table view in the Large View overlay:
Screen Shot 2023-10-23 at 2 29 39 PM

The correct table view is available from a Display Layout's "Large View":
Screen Shot 2023-10-23 at 2 32 12 PM

Environment

  • Open MCT Version: 3.0.2, 3.2.0
  • Deployment Type: all
  • OS: all
  • Browser: all

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@charlesh88
Copy link
Contributor Author

Dupe of #7158

@unlikelyzero unlikelyzero added the invalid duplicate or incorrectly filed label Jan 17, 2024
@unlikelyzero unlikelyzero added this to the Wont Fix milestone Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid duplicate or incorrectly filed type:bug
Projects
None yet
Development

No branches or pull requests

3 participants