Skip to content

Warn user when scenario version is outdated before save or deploy #7702

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

Closed
DeamonDev opened this issue Mar 20, 2025 · 0 comments · Fixed by #7732
Closed

Warn user when scenario version is outdated before save or deploy #7702

DeamonDev opened this issue Mar 20, 2025 · 0 comments · Fixed by #7732
Assignees
Labels

Comments

@DeamonDev
Copy link
Contributor

💥 Proposal

Sometimes it may happen that user tries to

  • save scenario version after someone saved theirs version in another machine or browser tab
  • deploy of currently seen version while newer deployment was committed in the meantime

In both of these situations we should at least inform the user that current version is not being the latest one. Admittedly the scenario activities
are updated without need of page reload and are properly updated on their panel - but they might be unnoticed by the user.

@DeamonDev DeamonDev self-assigned this Mar 20, 2025
@DeamonDev DeamonDev changed the title Warn user before trying to perform action after other remote changes being performed during scenario edit Warn user before trying to perform while another changes were performed during scenario edit Mar 20, 2025
@DeamonDev DeamonDev changed the title Warn user before trying to perform while another changes were performed during scenario edit Warn user before trying to perform action while another changes were performed during scenario edit Mar 20, 2025
@DeamonDev DeamonDev changed the title Warn user before trying to perform action while another changes were performed during scenario edit Warn user when scenario version is outdated before save or deploy Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant