You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create a notebook shift log
create an entry
click Commit Entries located in the lower right of the notebook
Observe an object lock icon in the upper right
Observe you cannot edit the name of the notebook but you should be able to
Click the object lock
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
e triage -->
The text was updated successfully, but these errors were encountered:
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
Steps to Reproduce
Commit Entries
located in the lower right of the notebookEnvironment
Impact Check List
Additional Information
e triage -->
The text was updated successfully, but these errors were encountered: