Feature Wiki
Tabs
Global Setting for News Period in Container-Objects
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
1 Initial Problem
Often Container-Objects are used for a long time and if News are used, it is possible that a lot of News are piling up over time.
To limit the presented News of a Container-Object, there is the setting "Show News After" at [Object] ›› News Settings. This setting allows you to enter an absolute date. Over time, this absolute date gets outdated - if you want to limit the presented time period in a relative way, you will have to change the absolute date regularly.
In addition, this settings exists only locally at every Container-Object and can't be set globally for all Container-Objects.
2 Conceptual Summary
A new global setting is introduced, which allows administrative accounts to define a global standard for the 'Container-Objects News Period'. This settings has the same options as 'Dashboard News Period' and in additionally 'Do not limit news' as this was the standard in the past.
This settings directly affects the presentation of the News at Container-Objects, if the option 'Use global setting' is selected. At those settings, three new options are introduced and the setting will be switched from a checkbox to a radio group:
- Use global setting
- Do not limit news (as it was the standard before without having the checkbox 'Show News After' activated)
- Show News After (this option was given in the past)
- Show News by Period
This new setting only affects the presentation of news. In order to delete old news completely, there is a separate Feature Request Cron Job: Delete old News Entries.
3 User Interface Modifications
3.1 List of Affected Views
- Administration ›› Communication ›› News and Web Feeds
- [Container-Object] ›› Settings ›› News Settings
3.2 User Interface Details
For details please have a look at chapter 2. Conceptual Summary.
3.3 New User Interface Concepts
None.
3.4 Accessibility Implications
None.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Samoila, Oliver [oliver.samoila]
- Authority to Sign off Code Changes: Joußen, Thomas [tjoussen]
4.2 Technical Aspects
Reducing the amount of data stored and the amount of data to be processed should result in a positive impact on performance.
4.3 Privacy
None.
4.4 Security
Nothing specific.
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila]
4.6 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 this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
Kruse, Fabian [Fabian], June 29 2026: I appreciate this suggestion, but the radio group seems a bit random, having to choose between limiting news to either one week, one month, or one year. Specifically, the gap between one month and one year seems huge.
Maybe it could be viable to offer a text/number entry field to be able to select any number of weeks?
JourFixe, ILIAS [jourfixe], 29 JUN 2026: We highly appreciate this suggestion and schedule the feature for trunk. In case we notice in practice, that the gap between one month and one year is too big, we still can add three and six month – but then in all similar dropdowns within the system to keep consistency.
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 29. Jun 2026, 14:23, Kunkel, Matthias [mkunkel]