Closed Bug 274362 Opened 20 years ago Closed 15 years ago

Ability to set task duration independent of due date.

Categories

(Calendar :: Tasks, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 512426

People

(Reporter: gekacheka, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: 

A requested feature is the ability to for scheduled tasks to appear in the
calendar views.  (Bug 157274)

Need be able to schedule a task to a period which ends long before the task is due.

Reproducible: Always
Steps to Reproduce:
1. New Task
2. fill Start date, time when I plan to start the task.
3. fill Due date, time when the task is due.
4. OK.

Actual Results:  
Task box could fill all the time between the start date and the due date.


Expected Results:  
Add a duration.  Then task fills time in the calendar from start time until
start time + duration.

Workarounds:
A. schedule every task in the hour before it is due.  (unrealistic)
B. set the due date to the end of the scheduled period (loses due date, and
alarms based on due date, and coloring based on whether the due date has past.)


DataModel

This requires adding duration to the todo/task data model.  (Currently due date
is aliased as end date, and duration is just the difference between start and
end date.  This may make sense for events, but is not suitable for tasks.)
Blocks: 157274
The item dialog proposed in bug 298102 implements todo/task end dates by
setting/getting the experimental property X-DTEND.
Depends on: 298102
QA Contact: gurganbl → general
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Component: General → Tasks
QA Contact: general → tasks
bug 328216 is related but originally different. 

* bug 274362 (this bug): set duration and/or due date (possible to set both)

  (use X-property to get around rfc2445§4.6.2, which says can't have both.
   e.g, events display from DTSTART to DTEND, the duration interval; 
   tasks could display from DTSTART to X-DTEND, and also have an 
   independent DUE date.  Alternative is to use x-duration, but that might
   require more computation for searches [which tasks are in view].   Both
   assume that due date is more important than duration for interoperability.)

* bug 328216: set duration instead of due date (never set both)

  (within rfc2445§4.6.2)

Fixing bug 238216 (as originally proposed) would not fix this bug.

(Note: bug 238216 comment 12 to 18 are offtopic/wrong-bug)
I think we should stick with the specs. Marking as duplicate of bug 512426, which implements Duration UI
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.