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

Quality Level Does Not Persist #1095

Open
weibullguy opened this issue Jun 16, 2022 · 0 comments
Open

Quality Level Does Not Persist #1095

weibullguy opened this issue Jun 16, 2022 · 0 comments
Labels
bump: patch Issue or PR documents a bug fix or enhancement requiring a patch version bump. dobranch Create issue branch when issue is assigned. priority: high Issue or PR is high priority. status: backlog Issue or PR is open, unmilestoned, and unassigned. type: fix Issue or PR affects existing functionality.
Milestone

Comments

@weibullguy
Copy link
Collaborator

weibullguy commented Jun 16, 2022

Describe the bug
The selected quality level for MIL-HDBK-217F does not persist after the component is deselected in the module view. The value is being changed and will save to the connected program database, but the combo box is not being updated.

Expected Behavior
As a RAMSTK analyst, I want widgets to be loaded with database data so that I know the data exists and is the correct value.

Actual Behavior
The quality combo box is not updated when a component is selected.

Reproduce

  1. Launch RAMSTK
  2. Open a program database
  3. Select the Hardware module
  4. Select a component
  5. Select a quality level
  6. Select a different line in the Hardware module view
  7. Select the original component

Logs
None

Additional Comments
None

dobranch
bump: patch
priority: high
type: fix

@github-actions github-actions bot added bump: patch Issue or PR documents a bug fix or enhancement requiring a patch version bump. dobranch Create issue branch when issue is assigned. priority: high Issue or PR is high priority. status: backlog Issue or PR is open, unmilestoned, and unassigned. type: fix Issue or PR affects existing functionality. and removed type: fix Issue or PR affects existing functionality. labels Jun 16, 2022
@weibullguy weibullguy added the type: fix Issue or PR affects existing functionality. label Jun 16, 2022
@weibullguy weibullguy added this to the v1.0.0 milestone Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump: patch Issue or PR documents a bug fix or enhancement requiring a patch version bump. dobranch Create issue branch when issue is assigned. priority: high Issue or PR is high priority. status: backlog Issue or PR is open, unmilestoned, and unassigned. type: fix Issue or PR affects existing functionality.
Projects
None yet
Development

No branches or pull requests

1 participant