Moodle
  1. Moodle
  2. MDL-25647

Peer Services Settings not saving

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.1
    • Component/s: MNet
    • Labels:
    • Database:
      MySQL
    • Difficulty:
      Easy
    • Affected Branches:
      MOODLE_20_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      Peer Services Settings not saving
      Peer service settings are lost after trying to save them. All boxes remain checked after saving, even if they have been unchecked before saving.

        Gliffy Diagrams

          Activity

          Hide
          Eloy Lafuente (stronk7) added a comment -

          Moved to stable backlog, raised to critical (lost of data).

          Thanks for reporting, this will be handled soon, ciao

          Show
          Eloy Lafuente (stronk7) added a comment - Moved to stable backlog, raised to critical (lost of data). Thanks for reporting, this will be handled soon, ciao
          Hide
          David Mudrak added a comment -

          Assigning back to myself. Sorry but this issue was created per my request in the forum and I am in contact with the reporter. I do not understand why it was re-assigned from me...

          Show
          David Mudrak added a comment - Assigning back to myself. Sorry but this issue was created per my request in the forum and I am in contact with the reporter. I do not understand why it was re-assigned from me...
          Hide
          Jérôme Mouneyrac added a comment - - edited

          It was reassigned from you because the issue was selected during our first spring meeting. Some STABLE backlog issues with high priority were reassigned to moodle.com and in the Spring pool. Then everybody from the Spring team pick some moodle.com issues from the Spring pool, fix it, pick another one, fix it ... till the end of the spring. Obviously it's our first spring ever so Agile processes will improve with the time

          I'll let people know about that during our daily spring meeting. Thanks.

          Show
          Jérôme Mouneyrac added a comment - - edited It was reassigned from you because the issue was selected during our first spring meeting. Some STABLE backlog issues with high priority were reassigned to moodle.com and in the Spring pool. Then everybody from the Spring team pick some moodle.com issues from the Spring pool, fix it, pick another one, fix it ... till the end of the spring. Obviously it's our first spring ever so Agile processes will improve with the time I'll let people know about that during our daily spring meeting. Thanks.
          Hide
          Jérôme Mouneyrac added a comment -

          A quick note, once is it in PULL request, the spring issue should be marked as Done (== IN PULL REQUEST). If the pull request is rejected, the issue must be reopened. It's temporary till we have some better greenhopper columns

          Show
          Jérôme Mouneyrac added a comment - A quick note, once is it in PULL request, the spring issue should be marked as Done (== IN PULL REQUEST). If the pull request is rejected, the issue must be reopened. It's temporary till we have some better greenhopper columns
          Hide
          Petr Skoda added a comment -

          closing, thanks

          Show
          Petr Skoda added a comment - closing, thanks

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: