Feature Request: Implement Autosave for Finding Edits

[fvelazquez-X]

Description:
Currently, while editing a finding, changes are only saved when the user manually completes the edit process. This creates a risk of data loss if the user accidentally closes the edit window (e.g., by clicking outside), encounters a browser crash, or navigates away unintentionally.

Implementing an autosave mechanism would improve usability, reduce the risk of losing work, and create a more robust editing experience.

Proposed Behavior:

• Periodically autosave changes while the user is editing a finding (e.g., every X seconds or after each field change).
• Store autosaved drafts locally (e.g., in browser local storage or backend temporary storage) until the edit is finalized.
• Allow recovery of unsaved edits if the session is interrupted.
• Optionally indicate save status ("All changes saved", "Saving…") to the user.

Benefits:

• Minimizes data loss due to accidental closures, browser crashes, or navigation errors.
• Improves user confidence while editing.
• Aligns with modern UX patterns in data entry forms.

Considerations:

• Define reasonable autosave interval (e.g., 5-10 seconds).
• Handle conflicts if the same finding is edited in multiple sessions.
• Provide visual feedback of autosave status.

[roadside-picnicx]

I mentioned it in the issue I opened, but I might as well bump it up here. Any updates on the autosave feature?

[mesquidar]

Hi @fvelazquez-X @roadside-picnicx In the new dev image I introduced a new autosave feature (it's only applied at the moment on vuln creation and edit dialog). This feature saves a draft and It only applies the changes to the real db when you click on save

Regards :)