Possible Indication in Assignments Tab

1 Initial Problem

When checking an individual plan, you are alerted (both in the "View" and "Manage" view) if it isn't "possible" for an assignment to complete a study programme.
This may have two reasons:

• The points available in subnodes don't add up to the points an assignment needs to complete the topnode.
• Study programme nodes aren't containing any training link.

This request refers merely to the first situation but would be helpful in the second one, too.

In case you edit the individual plan of an assignment, you will see the consequences immediately.

However, the individual plan is also "edited" when you open subnodes and declare them as irrelevant for assignments.
In this case, you may well end up in making it "impossible" to complete the topnode for hundreds of users - and you will only be alerted on that when you open the individual plan of single assignments.

2 Conceptual Summary

There is a "Possible" indication also in the table of assignments.
This might be implemented in a way similar to the indication of inactive users.
There might also be a filter that allows to display only those assignments for which completion is impossible.

3 User Interface Modifications

3.1 List of Affected Views

• Study Programme > Assignments

3.2 User Interface Details

• A red note "Completion impossible with current plan" is displayed below the username of an assignment (similar to the note displayed for inactive users).
• A filter "Completion possible" is offered that allows to choose from "All" (initial value), "Yes" and "No".

3.3 New User Interface Concepts

Research is necessary whether it would be possible to show "Completion impossible with current plan" and "Inactive user" as well.

3.4 Accessibility Implications

s. above

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 Privacy

none

6 Security

none

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: Klees, Richard [rklees]
• Implementation of the feature is done by: Klees, Richard [rklees]

8 Funding

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

• …

9 Discussion

10 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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.