Feature Request: Enhance Scheduled Task Options

[jvanis]

I have done some searching and not seen this mentioned before.

Request: More Options for Scheduled Task abilities, specifically:

• Move/Rename/Delete Files/Folders From that specific AMP Instance OR the entire AMP directory

Example Using an existing Schedule, Add a New Task named FileMovement Input: Select Dropdown (Copy File, Delete File, Move File, Copy Directory, Delete Directory, Move Directory) - Copy File

• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root Instance Folder)/Minecraft/world/data/file.text)
• To Path: Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root Instance Folder)/Minecraft/world/data/backup/file.text) - Delete File
• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root Instance Folder)/Minecraft/world/data/file.text) - Move File
• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root Instance Folder)/Minecraft/world/data/file.text)

• To Path: Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root Instance Folder)/Minecraft/world/data/file.text)

  - Copy Directory

• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root AMP Folder)/Instance01/Minecraft/world/data/)
• To Path: Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root AMP Folder)/Instance02/Minecraft/world/data/backup/) - Delete Directory
• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root AMP Folder)/Instance01/Minecraft/world/data/) - Move Directory
• From Path : Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root AMP Folder)/Instance01/Minecraft/world/data/)
• To Path: Root Path = instance folder if used from the specific instance or AMP path if used from the main AMP Page (Ex: (Root AMP Folder)/Instance02/Minecraft/world/data/backup/)

[leasoncre]

The UI in general needs a fairly major overhaul for the scheduler. Here's some ideas i have for general ease-of-use:

1. EDITABLE: Both the trigger and the tasks should be editable. (i wouldn't expect that you'd need to change the type of trigger or type of task. But the content there of should be.

   • ie: a Time-based task should be allowed to change the time/dates
   • ie: an action's value Ie: command line text, should be editable -if you want to change the type of task, depending on the value type entered, you might be able to change the type of task.
   • +change the description/name of the trigger

2. VISABILITY: Trigger Values are not currently visible at all. The only way i currently know what the trigger is is with it's description/name that i set when i made it. (At the very least, being able to EDIT the trigger would show it's settings/values)

3. TEST: Add a simple button to run the task manually when clicked to run the tasks [Now]. (+Permission)

4. SORT/GROUP: (less of a priority to the above, but would be great functionality:) Sort: Sort/Filter Triggers by Name, Time, Other applicable values.

   • currently triggers do not follow any sorting order. Group: Ability to group sets of triggers into one block to easily manage/organize them
   • great if you have a number of tasks set to go off at various times, but all do generally the same thing. ex: Multiple server restart notices to players, followed by actual restart command sent to console. ex: server cleanup tasks that run at different intervals could be in one group.

5. TIME: Display the current AMP/System Time in UI somewhere.

   • Optionally: Highlight the next task(s) scheduled to run in a different color (Green instead of blue?)
   • • Group coloring: Next group or non-grouped trigger(main list), then inside each group would highlight the next trigger(subset).
   • side note: Time UI is not currently able to handle longer than a weekly task. +Add support for custom intervals (x days/weeks/months/years, weekly/bi-weekly/monthly/bi-monthly,etc..) consider changing from graphical to text/numerical entry interface. (Microsoft's Task Scheduler might be a good reference point)
   • • date start, date end, doesn't end (trigger only runs for x period)

6. SIZE/MANAGEABILITY: Shrink/Minimize/Contract a group or single trigger:

   • if you have ALOT of triggers in your schedule, minimizing groups/triggers to a single line would make managing them alot easier on the eyes. (Display only group/Trigger Name with a [+] / [-] button)
   • • minimize all, expand all, minimize groups, expand groups,
   • great for keeping track of what trigger you 'reviewed' already, as well as less clutter.

7. CONTROL:

   • Enable/Disable a single trigger from running entirely (still keeping it in the list), highlight in a muted red color)
   • Enable/Disable groups of triggers (+Permission)
   • Enable/Disable ALL (+Permission, Admin command)
   • Delete Group (+Permission, Admin command, if empty perm not needed?)
   • Delete ALL (+Permission!, Admin command)

8. RETAIN: Optionally: save the current view for the user automatically (all sort/filter and minimize/expand settings) - not enabled by default? not saved per-user(use global save)? (only really needed for larger lists and piece of mind)

[Greelan]

On point 5, Webmin's cron scheduler might be another reference point. See attached screenshot. It allows multiple Minutes, Hours, Days, Months and Weekdays to be selected, giving lots of flexibility for combinations.

[TorStava]

It would be great if it's an option to enter the time schedule manually in CRON format instead of having to click around in the GUI.