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

Unable to create new Condition set #4542

Closed
2 of 5 tasks
nikhilmandlik opened this issue Dec 7, 2021 · 3 comments · Fixed by #4598
Closed
2 of 5 tasks

Unable to create new Condition set #4542

nikhilmandlik opened this issue Dec 7, 2021 · 3 comments · Fixed by #4598
Assignees
Labels
bug:regression It used to work. Now it doesn't :( severity:blocker type:bug
Projects

Comments

@nikhilmandlik
Copy link
Contributor

nikhilmandlik commented Dec 7, 2021

Summary

unable to create new condition set on /latest

Expected vs Current Behavior

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?

Steps to Reproduce

  1. open openmct
  2. try to create new condition set
  3. ok button is always disabled

Environment

  • Open MCT Version:
Version: 1.8.1-SNAPSHOT
Build Date: Tue Dec 07 2021 12:35:02 GMT-0800 (Pacific Standard Time)
Revision: 8acbcadd5d17e201f32f03deb753b8b12b591063
Branch: master
  • Deployment Type: VIPER
  • OS: MAC OS
  • Browser: Brave

Additional Information

@unlikelyzero
Copy link
Collaborator

Assigning myself to create an e2e test when this PR is opened

@nikhilmandlik
Copy link
Contributor Author

partially fixed, can create new condition but once created it should be in edit mode

@unlikelyzero
Copy link
Collaborator

Verified fixed but with #4600

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:regression It used to work. Now it doesn't :( severity:blocker type:bug
Projects
Development

Successfully merging a pull request may close this issue.

3 participants