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

Stacked Plots having configuration saved on load #5363

Closed
1 of 7 tasks
davetsay opened this issue Jun 16, 2022 · 3 comments
Closed
1 of 7 tasks

Stacked Plots having configuration saved on load #5363

davetsay opened this issue Jun 16, 2022 · 3 comments
Labels
needs:e2e Needs an e2e test performance impacts or improves performance severity:critical type:bug
Milestone

Comments

@davetsay
Copy link
Contributor

Summary

In general configurations should not be persisted unless the user explicitly makes a change.

Expected vs Current Behavior

Stacked plots should have a reasonable default configuration if it doesn't have one

Steps to Reproduce

  1. create a stacked plot object
  2. drag and drop telemetry into the stacked plot object and save
  3. open console browser and navigate to network tab
  4. navigate away from and then back to the stacked plot
  5. go into edit mode
  6. save the stacked plot
  7. you should not see a network PUT call to the persistence provider Couch
  8. go into edit mode again
  9. click on a plot in the stacked plot object
  10. modify properties in the plot series in the inspector (aka color of plot lines)
  11. save the plot
  12. now you should see a network PUT call to couch

Environment

  • Open MCT Version: release/2.0.5
  • Deployment Type:
  • 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

@alizenguyen
Copy link
Contributor

Verified Testathon 6/23/22

@ozyx
Copy link
Contributor

ozyx commented Jun 27, 2022

Verified Testathon 6/27/22

@davetsay
Copy link
Contributor Author

davetsay commented Jul 1, 2022

verified

@unlikelyzero unlikelyzero added performance impacts or improves performance severity:critical needs:e2e Needs an e2e test labels Jul 6, 2022
@unlikelyzero unlikelyzero added this to the Sprint:2.0.7 milestone Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:e2e Needs an e2e test performance impacts or improves performance severity:critical type:bug
Projects
None yet
Development

No branches or pull requests

5 participants