Skip to content

Improve logic of rerunning course steps #8690

@novoselt

Description

@novoselt

I could get to the following situation:

Image

What has happened:

  • all 133 students were assigned
  • then all were collected, but 6 have failed
  • I reassigned to all 133, which resulted in 7 errors, different from the 6 who have failed collecting

Now:

  • collect step thinks that collection was done for all but 6, 7 "new errors" are not taken into account
  • individually, I can redo collect step for all students EXCEPT those 7 for whom the second assignment didn't work
  • but with the run all button it seems that I can trigger collection for all 133
  • this is confusing...

The solution is to either make possible steps more straightforward, or explain the situation better.

"Straightfoward Option": if a previous step is redone, mark all next ones as incomplete, but it feels that deleting relevant files would be logical as well. But deleting files, potentially with manual edits, is not a good idea in general...

"Info Option": add a note that redoing a step, especially redoing it for all students, will cause consecutive steps to be out of sync and it is instructor's responsibility to keep track of it and fix it if necessary. This is basically the current situation, it just would make it more obvious.

Possible bonus: if there was a successful assignment, followed by an unsuccessful re-assignment, allow (re)collection anyway.

I am leaning towards the info option - redoing intermediate steps is potentially problematic without clear default choices, so just let instructors do whatever is necessary without artificial limits, but warn about issues.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions