Mail about expiring validity not sent if another assignment has qualification still valid longer

1 Initial Problem

Users can be assigned more than one time to study programmes and several of those multiple assignments can have a valid qualification.
By now, mail notification about expiring validity of a qualification is dispatched for each of the assignments, even if qualifications of their other assignments are still valid for a longer period of time.

Scenario
A user is assigned to a study programme on privacy rules a first time automatically, based on an org unit.
After some time he/she completes an associated course and now the achieved qualification is valid for 2 years (with a reminder about expiring validity 3 months before).
However, the privacy rules training might also be interesting to target groups not foreseen, so another assignment automation is established: Everyone participating in such a training is automatically assigned to the study programme.
After 1.5 years there is an opportunity for the user to participate in some training of the same topic again.
The user participates, is assigned, achieves a new qualification, so this assignment of him/her has a valid qualification for the next 2 years (the old one only for 6 more months).
3 months later, the user receives a reminder reading that his/her qualification threatens to fall invalid (which is true for the old assignment but false in the overall situation).

Analogy
I already received my new credit card some time ago but the bank notifies me that my old credit card is soon expiring. This notification is not needed.

2 Conceptual Summary

Mail notification about expiring validity of a qualification will not be sent if there is another assignment in the same study programme with a qualification still valid for a longer period of time (or unlimited).
No configuration option is required.

3 User Interface Modifications

3.1 List of Affected Views

• none

3.2 User Interface Details

none

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

none

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}

Approval

Approved at {date} by {user}.