Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-42168

Provide a "Save and Return" option on eventing editor

    XMLWordPrintable

Details

    • 1

    Attachments

      For Gerrit Dashboard: MB-42168
      # Subject Branch Project Status CR V

      Activity

        Jeelan Poola, are you proposing a two button approach, with "Save and Return", "Save" both showing up? Or are you proposing a single button that has a drop down for someone to select the non-default behavior (save and remain in edit mode)?

        srinivasan.raman Srinivasan Raman added a comment - Jeelan Poola , are you proposing a two button approach, with "Save and Return", "Save" both showing up? Or are you proposing a single button that has a drop down for someone to select the non-default behavior (save and remain in edit mode)?
        jeelan.poola Jeelan Poola added a comment -

        I am ok with 2 buttons. Is there a better option? Cc Jon Strabala.

        jeelan.poola Jeelan Poola added a comment - I am ok with 2 buttons. Is there a better option? Cc Jon Strabala .

        Jeelan Poola, Jon Strabala: Options would be either a 2 button approach, or a single button approach. In a single button approach, one option will show up by default ("Save and Return"). In the same button, we can have an arrow drop-down that shows this option as well as "Save" option.

        For folks working on larger scripts, they may wish to spend more time and hence may wish to save multiple times - a single button + dropdown approach will add one additional action for them.

        In my opinion, this functionality is primarily meant to be used using browsers on laptops / desktops - real estate is not a concern. Two button approach is better as a user can choose to save and return, or save and remain with just a single click.

        srinivasan.raman Srinivasan Raman added a comment - Jeelan Poola , Jon Strabala : Options would be either a 2 button approach, or a single button approach. In a single button approach, one option will show up by default ("Save and Return"). In the same button, we can have an arrow drop-down that shows this option as well as "Save" option. For folks working on larger scripts, they may wish to spend more time and hence may wish to save multiple times - a single button + dropdown approach will add one additional action for them. In my opinion, this functionality is primarily meant to be used using browsers on laptops / desktops - real estate is not a concern. Two button approach is better as a user can choose to save and return, or save and remain with just a single click.
        jeelan.poola Jeelan Poola added a comment -

        Srinivasan Raman I am fine with 'Save' & 'Save And Return' two buttons.

        jeelan.poola Jeelan Poola added a comment - Srinivasan Raman I am fine with 'Save' & 'Save And Return' two buttons.
        jon.strabala Jon Strabala added a comment - - edited

        When we are  editing an exisiting function we launch the code editor from the Eventing Summary Page thus two buttons

            Cancel [Save] [Save & Continue]

        The above makes perfect sense

        When we are Importing or adding a function we launch the code editor from the Functions settings thus

            [Save] [Save And Return]

        The above would work of course but we wouldn't return to settings in this case we return to the Eventing Summary Page (kind of like a stack of two returns)

        Perhaps we should use one of the below (and shouldn't one action be prominent - question for Rob Ashcom for best UX practices).

            Cancel [Save] [Save & Continue]
            Cancel Save [Save & Continue]

         

        jon.strabala Jon Strabala added a comment - - edited When we are  editing an exisiting function we launch the code editor from the Eventing Summary Page thus two buttons     Cancel   [Save] [Save & Continue] The above makes perfect sense When we are Importing or adding a function we launch the code editor from the Functions settings thus     [Save] [Save And Return] The above would work of course but we wouldn't return to settings in this case we return to the Eventing Summary Page (kind of like a stack of two returns) Perhaps we should use one of the below (and shouldn't one action be prominent - question for Rob Ashcom  for best UX practices).     Cancel   [Save] [Save & Continue]      Cancel   Save   [Save & Continue]  
        jeelan.poola Jeelan Poola added a comment - - edited

        Jon Strabala In order to keep things simple & intuitive, may I suggest below option always.
        [Cancel] [Save] [Save & Return]

        Essentially,
        clicking on Save code is saved & user will stay on the editor page.
        clicking on Save & Return code is saved & user will return to summary page.

        jeelan.poola Jeelan Poola added a comment - - edited Jon Strabala In order to keep things simple & intuitive, may I suggest below option always. [Cancel] [Save] [Save & Return] Essentially, clicking on Save code is saved & user will stay on the editor page. clicking on Save & Return code is saved & user will return to summary page.

        Build couchbase-server-7.0.0-4259 contains eventing commit 413f9ca with commit message:
        MB-42168: Provide a Save-and-return option in eventing editor

        build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-4259 contains eventing commit 413f9ca with commit message: MB-42168 : Provide a Save-and-return option in eventing editor
        sujay.gad Sujay Gad added a comment -

        Verified using Couchbase Server 7.0.0 - 4291
        Save and Return option added for eventing editor.

        sujay.gad Sujay Gad added a comment - Verified using Couchbase Server 7.0.0 - 4291 Save and Return option added for eventing editor.

        People

          srinivasan.raman Srinivasan Raman
          jeelan.poola Jeelan Poola
          Votes:
          0 Vote for this issue
          Watchers:
          8 Start watching this issue

          Dates

            Created:
            Updated:
            Resolved:

            Gerrit Reviews

              There are no open Gerrit changes

              PagerDuty