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

[Notebook] Commiting Shift Logs is indicating object lock #7942

Open
1 of 7 tasks
davetsay opened this issue Dec 5, 2024 · 0 comments
Open
1 of 7 tasks

[Notebook] Commiting Shift Logs is indicating object lock #7942

davetsay opened this issue Dec 5, 2024 · 0 comments
Labels

Comments

@davetsay
Copy link
Contributor

davetsay commented Dec 5, 2024

Summary

Clicking the Commit Entries button in Notebook Shift Logs will display an object lock, which it shouldn't. That lock also at least prevents editing name from the browse bar (not sure what other functional impact it has). Clicking the lock icon will remove it.

Expected vs Current Behavior

  • Commit Entries only should lock the current page from editing.
  • No object lock should be visible
  • No unintended object level functionality should be changed.

Steps to Reproduce

  1. Create a notebook shift log
  2. create an entry
  3. click Commit Entries located in the lower right of the notebook
  4. Observe an object lock icon in the upper right
  5. Observe you cannot edit the name of the notebook but you should be able to
  6. Click the object lock
  7. Observe the lock is gone, and you can resume editing

Environment

  • Open MCT Version:
  • 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

Screenshot 2024-12-04 at 4 57 33 PM
e triage -->

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant