Feature Wiki

Information about planned and released features

Tabs

Abandon «Drafts» in Forum

1 Reasons to Abandon Feature

Forums should become free of the complexity of drafts.

If "Drafts" are globally activated for forums, functions are provided with which …
… drafts for threads can be created,
… drafts for postings can be created,
… drafts can then be edited again at the level of the entire forum or individual topics,
… drafts of threads are presented in a separate view, drafts of postings in the context in which they were created.
… the final publication is made in different places in different ways.
… the number of drafts in the entire object is displayed in the repository or on dashboard.

The complexity of the functions described is now further increased with an autosave function.

In addition to creating threads or postings, you can also create drafts, actively save drafts manually, save drafts via autosave, and revert drafts that have been saved via autosave to an earlier draft status by cancelling the changes actively. If a draft is to be called up again without explicitly saving it, different versions are made available for further editing.

The screenshot with the list of test cases shows very well the variations that are created here.
 

The drafts are a complete second layer for the code in the forum, which needs to be fully considered with every idea for further development or modification - and which needs to be maintained! 
    

The feature is inactive by default. In random checks on platforms, only very few have been found on which the feature has been activated at all. Nothing is known about the intensity of use.
        

Forum Administration
Drafts Part of Test Suite in TestRail
Posting Draft with activated Autosave
Thread Draft
Saved Posting Draft in Thread-View
Number of Drafts in ListGUI
Access to Thread Drafts
List of Thread Drafts

2 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.}

3 Contact

4 Funding

Removing the feature from the ILIAS code base might need funding. If you are interest in funding this request, please add your name and institution to this list.

  • ...

5 Discussion

Use the following discussion section to express your objections against this request or your consent to get rid of this feature.

6 Implementation

{The maintainer has to give a 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: 9. Feb 2024, 09:12, Samoila, Oliver [oliver.samoila]