Feature Wiki
Tabs
Test: Abandon Personal Default settings
Page Overview
[Hide]- 1 Reasons to Abandon Feature
- 2 Additional Information
- 2.1 Involved Authorities
- 2.2 Technical Aspects
- 2.3 Contact
- 2.4 Funding
- 3 Discussion
- 4 Implementation
1 Reasons to Abandon Feature
The Personal Settings "storing" Feature is a rather old feature which uses a lot of legacy UI elements. The transformation to new UI Elements is expensive.
Also, the feature does not show, which settings are stored within its storing points.
Therefore, we have plenty of issues if new settings are introduced or something is changed.
Additionally the information is stored in a serialized format in the database which leads to difficult to solve issues on every change of the settings.
We created this article in consultation with the project manager of RLUI. Please also his statement in this Mantis Issue: #43729
2 Additional Information
2.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Strassner, Denis [dstrassner]
- Authority to Sign off Code Changes: Kergomard, Stephan [skergomard], Joußen, Thomas [tjoussen], Becker, Maximilian [mbecker]
If this request is related to multiple components, please list both authorities for all related components.
2.2 Technical Aspects
{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components and necessary modifications in general services/architecture. }
2.3 Contact
Person to be contacted in case of questions about the request or for funding offers: Strassner, Denis [dstrassner]
2.4 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for abandon this feature, please get into contact with the person mentioned above as 'Contact'.
3 Discussion
Use the following discussion section to express your objections against this request or your consent to get rid of this feature.
JourFixe, ILIAS [jourfixe], 17 FEB 2025: We follow the suggestion of Denis and accept to abandon this feature with ILIAS 11. We keep the final decision open until 23 June 2025. This will give all interested stakeholders a chance to create a suggestion how the underlying process of taking over settings to new tests could be implemented safely and feasible. This might allow us to exchange this feature by a better and more stable one. If you are interested to keep this feature (not the code), please start to create a suggestion and call for a related feature workshop in the near future.
Hackfort, Marvin [m.hackfort]: We are actively using it, when working with our tests to put the same settings very quickly in every test on our e-Assessment platfform. I understand, that this uses a lot of old UI elements, but rather than abandoning it, I would like to discuss an option to rework this. Maybe this can be implemented slimmer than before. As we are interested in keeping this, we would also help fund this project.
4 Implementation
{Short description of the final implementation and possible consequences for existing installations.}
Removed Testcases
The following testcases have been removed from Testrail or modified because the feature is no longer part of the ILIAS core.
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 26. Mar 2025, 14:06, Lowe, Simon [simon.lowe]