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

Audit changeset when variableset is modified shows too many changes #8521

Closed
susanpann opened this issue Dec 6, 2023 · 2 comments
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@susanpann
Copy link
Contributor

Severity

sev-3-low

Version

master

Latest Version

I could reproduce the problem in the latest build

What happened?

The audit changeset for modifying library variable sets shows too many changes. The variables are out of order, which may contribute.

Reproduction

  1. Create a library variableset with at least 1 sensitive variable and a few other variables.
  2. Modify the value of just one of the other variables.
  3. Navigate to audit > select the "variable set" document type filter and find the modify variable set event
  4. See that the changeset includes more changes than were made

Error and Stacktrace

No response

More Information

Changeset when only 1 variable was changed

Screenshot 2023-12-07 at 7 53 40 am

Workaround

No response

@susanpann susanpann added the kind/bug This issue represents a verified problem we are committed to solving label Dec 6, 2023
@octoreleasebot
Copy link

Release Note: When auditing variable changes, the variable list maintains a consistent order across the two versions, allowing for a more straightforward comparison of the underlying changes.

@Octobob
Copy link
Member

Octobob commented May 16, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.2 2024.2.7476
2024.3+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

4 participants