In the „Name” field, type a task name and in the „Duration” field, enter the time required to complete the task, as a number followed by „m” for minutes, „h” for hours, „d” for days, „w” for weeks or „mo” for months.

Elapsed time
In iTaskX it is possible to model duration in terms of „elapsed” duration. Elapsed duration is used when a task’s duration needs to disregard any „nonworking time” or resource constraints. For example, if you need a task to be scheduled over 10 consecutive days including weekends and ignoring resource availability you could set the duration to „10 ed”. An example where this feature is particularly useful is when you are modeling delays or „lags” in iTaskX. A „lag” is used to model an external delay. For example, „Waiting for a package to be delivered” or „Waiting for paint to dry”. Neither of these activities require any „work effort” but they do affect the duration of the project. So if you are waiting for a task such as „Paint to dry” before you can „Apply second Coat” you can make use of the elapsed days to model this delay or „lag” as the paint can dry regardless of whether it is the weekend or if it falls on a holiday. To create elapsed durations, enter the time required to complete the task, as a number followed by „em” for elapsed minutes, „eh” for elapsed hours, „ed” for elapsed days, „ew” for elapsed weeks or „emo” for elapsed months.