Unsaved Changes Notification

Description

Purpose: To implement an "unsaved changes" confirmation that will notify users that they are leaving a form with unsaved changes and ask them if they want to save or not.

User Story
As a FOLIO user
I want to know if I am leaving a form with unsaved changes
So I can save the changes if desired

Scenarios

  1. Scenario

    • Given the create or edit user form with unsaved changes

    • When I navigate away from the page by clicking another navigational element in FOLIO OR using the back button in the browser

    • Then I am presented with an unsaved changes notification (see attached screenshot)

      • Text: Save changes?

      • Buttons:

        • -Save changes - Saves changes and allows user to navigate as indicated-

        • Discard changes - Discards changes and allows user to navigate as indicated

        • Cancel - Closes notification popup and leaves user on create/edit user page. Unsaved changes remain and are unsaved.

  2. Scenario

    • Given the create or edit item form with unsaved changes

    • When I navigate away from the page by clicking another navigational element in FOLIO OR using the back button in the browser

    • Then I am presented with an unsaved changes notification (see attached screenshot)

      • Text: Save changes?

      • Buttons:

        • -Save changes - Saves changes and allows user to navigate as indicated-

        • Discard changes - Discards changes and allows user to navigate as indicated

        • Cancel - Closes notification popup and leaves user on create/edit user page. Unsaved changes remain and are unsaved.

  3. Scenario

    • Given I navigate away from a create or edit form with unsaved changes AND validation errors are present (invalid or required fields)

    • When I click the "Save changes" button in the unsaved changes notification

    • Then the notification closes and returns user to the create/edit user page where they can view and correct any validation errors and retry their save

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Jeremy Huff May 8, 2017 at 2:04 PM

This is good to go for the demo. I am finishing up some styling today, but that is it.

Jakub Skoczen May 8, 2017 at 1:34 PM

what is the status of this issue? Is there any hope to demo this tomorrow?

Cate Boerema May 4, 2017 at 1:41 PM
Edited

Per discussion in the FOLIO roundup today, we have decided to remove the scenarios related to the Save changes button and add them to a new story: LIBAPP-213. Jeremy has a pretty good idea of what will be needed to support that so he can add notes and dependencies there.

Cate Boerema April 11, 2017 at 8:53 AM

Makes sense. Keep me posted on the decision so I can break out a separate story.

Jakub Skoczen April 10, 2017 at 2:28 PM

As discussed on the UI roundup – if issues related to STRIPES-111 prevent reliable implementation of "Save changes" in the pop-up (due to the issues related to figuring out whether the compound status of the update was correct or not) let's omit it and support only "Cancel" (and continue editing) and "Discard" (and navigate away).

Done

Details

Assignee

Reporter

Priority

Sprint

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 31, 2017 at 1:35 PM
Updated July 20, 2017 at 1:21 PM
Resolved May 11, 2017 at 12:05 PM
TestRail: Cases
TestRail: Runs