Sortable Task List

1 Initial Problem

The current suggestion of a task list (see Introducing Task Service and Queuing Derived Tasks) has the following structure:

• Headline: Tasks to Complete
• Sub-Headline: Appointed Tasks
• List of Tasks
• Sub-Headline: Not-Appointed Tasks
• List of Tasks

Having two lists of tasks that are distinguished by the criteria if a task has a deadline or not takes us the possibility to let the user sort the tasks according to onw needs. And from the usability point of view, appointed tasks are easily indicated nevertheless as they clearly show that there is a deadline while not-appointed tasks have it not. But in daily use it is more helpful when I can cluster tasks sometimes by the kind of task (titel) and sometimes by deadline.

2 Conceptual Summary

1. There should only be one task list that contains all type of tasks.
2. Task list should become a sortable list of entries.
3. Sorting criterias are:
   • Title of task (e.g.: »Submit Assignment "Diagnostic Manual" in Exercise DSM-5«)
   • Deadline (next upcoming task is listed first, followed by others and non-appointed tasks are always listed after those with deadline when "Sorting by Deadline" is chosen)

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

I think this is a good idea and will improve the task list. I also think there should be a possiblity for users to hide a task, because at present I see an assignment in my task list as long as the deadline has not been reached - even if I have already uploaded my submission. This gives me the impression that I still have something to do here, which is not the case.
I think it would be more user-friendly and rewarding if an assignment dissapears form the task list as soon I have submitted something.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.