Single- and multi-task challenges are currently handled separately in different data structures. This results in duplicate production code (also different report templates) and also the testing effort is doubled. To decrease the maintenance effort, the idea is to represent a single-task challenge as a multi-task challenge with one task. This can be realized in the challenge class. In the challenge constructor an argument for a task name can be forced when the argument "by" specifying a multi-task challenge is missing. So the single-task challenge will also show up in an appropriate way in the multi-task challenge report.
Do you also think this makes sense? Am I missing something?