Categorizing Cron-Jobs

1 Initial Problem

By now (ILIAS 5.2.x) there are already 23 cron-jobs available in ILIAS.

There are only poor means to gain an overview of what cron-jobs exist and are used in what context, which ones are running, are okay etc.
The "Component" column at least is offering means to sort. However, the terminology is very technical, so this won't be of great use.

Moreover, there is no filter.
As the future might bring numbers of additional cron-jobs, this could become important.

And finally, it should be possible to hide/show columns and to save specific views.

2 Conceptual Summary

I reviewed the list and made proposals to categorize cron-jobs in a more intuitive way:

In addition, I propose to add:

• A filter
• An option to hide/sho columns
• An option to save a specific view (incl. filter and column selection)

3 User Interface Modifications

3.1 List of Affected Views

adm/cron_jobs/

3.2 User Interface Details

• Filter for cron-jobs, featuring the familiar handling (hide/show, apply/reset) and filter fields for:
  • The categories proposed in my file.
  • Status (active/inactive)
  • Schedule
  • Result
• Hide/show columns (as familiar from LP tables)
• Save views (as familiar from LP tables)

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 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

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

• ...

7 Discussion

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