Bug #5002

Assignments: when browsing through assignments through "previous submitter" - "next submitter", you get strange behaviour

Added by Liesbeth De Blaere over 9 years ago. Updated over 9 years ago.

Bug resolved
Liesbeth De Blaere
Start date:
Due date:
% Done:


Estimated time:


Assignments: when giving feedback / scoring through "previous submitter" - "next submitter" shows strange behaviour.

- The system doesn't count 1 - 2 - 3 etc
- Students get a different "ranking" almost every time (e.g. Anneleen is first student 3, then all of a sudden student 2, later on she's student 4...)



Updated by Stefaan Vanbillemont over 9 years ago

  • Assignee set to Anthony Hurst

Updated by Stefaan Vanbillemont over 9 years ago

  • Target version changed from Backlog (default) to LCMS 3

Updated by Anthony Hurst over 9 years ago

  • Status changed from New to Needs testing
  • Assignee changed from Anthony Hurst to Liesbeth De Blaere

I'm not entirely sure what you are trying to describe here. It may be that there is a misunderstanding about the functionality provided.

I have described the intended functionality below. I would be more than happy to take another look if, after retesting, you still believe the behaviour to be contrary to that intended.

In the higher level where there is a navigator (without next/previous submission), the navigator loops through all users, irrespective of whether they have submitted something or not.

In the deeper level (with next/previous submission), the navigator only loops through the submitters who have submitted something. To avoid random jumps in numbering, all submitters with submissions are numbered sequentially from 1, with other submitters (without a submission) pushed to the end and inaccessible:

If there are 7 submitters with submissions out of a total of 20 registered for the publication, those with submissions are numbered 1-7 (accessible), those without are numbered 8-20 (inaccessible).

If, while looping through the users, a submission is added by a submitter who previously had none, they are instantly added to the set of submitters with submissions. This can cause the effects you mentioned. Simultaneously looping through the submitters and removing a submission will produce similar jumps in numbering.


Updated by Liesbeth De Blaere over 9 years ago

  • % Done changed from 0 to 100

Updated by Stefaan Vanbillemont over 9 years ago

  • Status changed from Needs testing to Bug resolved

Also available in: Atom PDF