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.

Sign up for GitHub

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

Jump to bottom

BugFix - 39087 - Virtual Runset Not Showing As Dirty #3606

Merged
merged 2 commits into from
Apr 11, 2024
Merged

BugFix - 39087 - Virtual Runset Not Showing As Dirty #3606

merged 2 commits into from
Apr 11, 2024

Commits on Apr 11, 2024

  1. Bug: When we load a virtual runset and move to some other runset then… 

    …, we are not getting popup to save the dirty runset before moving to another one.

RC: Runset's dirty status is getting changed to NoChange when Dirty Tracking is started again.
Fix: Explicitly set the dirty status of Runset to Modified after loading a virtual runset on NewRunSetPage.
    @IamRanjeetSingh
    IamRanjeetSingh committed Apr 11, 2024
    Configuration menu
    Copy the full SHA
    da1708c View commit details
    Browse the repository at this point in the history

  2. Merge branch 'Releases/Beta' into BugFix/39087-NoPopupToSaveDirtyVirt… 

    …ualRunset
    @IamRanjeetSingh
    IamRanjeetSingh authored Apr 11, 2024
    Configuration menu
    Copy the full SHA
    42a6b46 View commit details
    Browse the repository at this point in the history