Ticket #375 (closed enhancement)

Opened 4 years ago

Last modified 4 years ago

Scheduler - Erase at modification

Reported by: jackjack Owned by: Joel
Priority: minor Milestone: Eraser 6.0.8
Component: User Interface (UX) Version: 6.0.7.1893
Keywords: Cc:
Processor Architecture: i386 (32-bit) Blocked By:
Blocking: Operating System: Windows XP

Description

When adding a schedule have the time default to 00:00 rather than current time of adding task

Alternatively (and less ideally) if schedules are going to insist on taking the seconds from the current time the task is created at least give the user a way to manually edit the seconds in the "Run this task at" field.

Blocking

IdSummaryMilestone
#375Scheduler - Erase at modificationEraser 6.0.8

Blocked by

IdSummaryMilestone
#375Scheduler - Erase at modificationEraser 6.0.8

Change History

comment:1 Changed 4 years ago by Joel

  • Component changed from BlackBox to User Interface (UX)
  • Milestone set to Eraser 6.0.8

The "run this task at" field is only valid when the task is a recurring task. If the task is not recurring, then the field is meaningless. If you select a recurring task, the seconds field is indeed editable.

I have this feeling I've misinterpreted your problem -- so if this isn't what you meant, please do elaborate.

comment:2 Changed 4 years ago by jackjack

To clarify, this is for recurring tasks.

This is two issues really, so perhaps it might want to be split.

1) Instead of defaulting to "current time" for a recurring schedule, have it default to 00:00 and let the user change it.

2) Eraser includes seconds into the scheduled run time based on the time the task was created (hh:mm:ss) but only gives the user a way to manipulate the hours and minutes. It would be nice to drop seconds out of the equation or give the user the ability to manipulate ss along with the hh and mm.

I would like to see the inclusion of seconds dropped

comment:3 Changed 4 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel
  1. Why is midnight preferred over the current time?
  2. I see your problem. The resolution of the scheduler is currently 30 seconds anyway, so yes, it's mainly the display of the seconds in the next run column that you are taking up.

I'll get 2. fixed.

comment:4 Changed 4 years ago by Joel

  1. fixed in r2257.

comment:5 Changed 4 years ago by Joel

  • Status changed from accepted to pending

comment:6 Changed 4 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.