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

Search result paths are often incorrect #5535

Closed
7 tasks
charlesh88 opened this issue Jul 19, 2022 · 1 comment · Fixed by #5567
Closed
7 tasks

Search result paths are often incorrect #5535

charlesh88 opened this issue Jul 19, 2022 · 1 comment · Fixed by #5567

Comments

@charlesh88
Copy link
Contributor

charlesh88 commented Jul 19, 2022

Summary

Paths in search results are being shown for the current object, not the result object. This happens while in browse or edit modes, and will sporadically correct themselves, although I see the improper behavior more often than the correct paths.

Screen Shot 2022-07-19 at 11 38 31 AM

Steps to Reproduce

  1. Use search to look for something that returns a number of results in a location that is clearly different from your current location.
  2. Note that the paths displayed for results may be the path to your current view's location, not the location of the result item.

Environment

  • Open MCT Version: R 2.0.5
  • Deployment Type: /testathon and running locally
  • OS:
  • Browser:

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

@akhenry
Copy link
Contributor

akhenry commented Jul 20, 2022

dupe of #5469 which has an outstanding PR

@charlesh88 charlesh88 changed the title Search paths are sporadically incorrect Search result paths are often incorrect Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants