Skip to content

Auto Saving Inconsistencies #681

Open
@vikasrohit

Description

@vikasrohit

With #659 application was supposed to remove support of auto saving for all fields except the specification field. However, it seems there are still few places where it is auto saving the challenge. Trying to have a list of what is saved automatically and what not.
Fields which are still auto saved:

  • Specification
  • Timeline template change
  • Reset Phases button immediately saves the phases

@acshields I think it is confusing what is auto saved and what is not. Should we just skip auto saving logic altogether. IMO, auto saving is good for documents but not for a complex object like challenge. If we only keep auto saving for the specification text/html, it still confuses users.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions