Moodle

Peer Services Settings not saving

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0
  • Fix Version/s: 2.0.1, STABLE sprint 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.

Issue Links

This issue will be resolved by:
PULL-18 Fixed checkbox handling at mnet peer services form Minor Accepted

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
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
Permalink
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
Permalink
Jerome 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
Jerome 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
Permalink
Jerome 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
Jerome 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
Permalink
Petr Škoda (skodak) added a comment -

closing, thanks

Show
Petr Škoda (skodak) added a comment - closing, thanks

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.5#665-sha1:422aead) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.