Returns the computed effective completion date for the Project, based on its local completionDate and those of its containers.Д®ffectiveDeferDateВ ( Date or null r/o).

If set, the project should be completed by this date.Д®ffectiveCompletedDateВ ( Date or null r/o).

If set, the project is dropped.ДueDateВ ( Date or null).

If set, the project is not actionable until this date.ДropDateВ ( Date or null).

If the propertyвЂ™s value is set to true, this is the Project that inbox tasks that have enough information specified (as selected by the userвЂ™s preferences) will be filed into upon a clean-up.ДeferDateВ ( Date or null).

If the propertyвЂ™s value is set to true, the project contains single tasks, and has no next task.ДefaultSingletonActionHolderВ ( Boolean).

If set, the project is completed.Д¬ontainsSingletonActionsВ ( Boolean).

If set, the project will be automatically marked completed when its last child Task is marked completed.Д¬ompletionDateВ ( Date or null).

Note that a project may be effectively considered completed if a containing project is marked completed.Д¬ompletedBењњhildrenВ ( Boolean)

True if the project has been marked completed.

An alias for the tasks property.Д¬ompletedВ ( Boolean r/o).

Returns a location referring to the position before the first Task directly contained in the root task of this project.Д¬hildrenВ ( TaskArray r/o).

Returns a location refering to position just before this project.Д«eginningВ ( Task.ChildInsertionLocation r/o).

An array of FileWrapper objects representing the attachments associated with the ProjectвЂ™s root Task.Д«eforeВ ( Folder.ChildInsertionLocation r/o).

Returns a location refering to position just after this project.ДЄttachmentsВ (Array of FileWrapper).Here are the properties of a project:ДЄfterВ ( Folder.ChildInsertionLocation r/o) Project PropertiesДЄs with most scriptable objects, instances of the Project class have properties that define their use and purpose. The Projects perspective displays all of your projects in a list, which can be grouped into folders to create hierarchy. Projects are typically more complex than individual action items, and can include several related actions. Tags might improve that but IвЂ™m not sure yet.A project is a task made up of multiple items, referred to in OmniFocus as actions. ItвЂ™s not that much time to do the context switching and works well. Since we have time constraints of doing chores if we have a lot of things to do we may blow off the less critical ones if more important ones take more time than expected. Right now I just check the local town context on the drive to the city (I am a passenger in the car, donвЂ™t do this and drive) and change the context to the city and back again if we donвЂ™t get the action done while there. (Our bank is local and only has a branch in the 2 local towns, for example) That way I could see errands that can be done in either place easily. My only use case is to flag the local town errands I can also do in the city with both places and vice versa. While itвЂ™s pretty clear that I can only get a lot of things at the further away city (which requires a whole day as weвЂ™ve got 3+ hours of drive time to get to and from) while there I can also do most of the errands from the local towns. The far away towns are where we do major shopping once a month. 1 is the 2 closest towns, sort of the run to town places less than 10 miles away and one is 2 towns that are a 1.5 hour drive to get there. I have a single action list Errands and I have 2 locations as contexts. I canвЂ™t really think of an instance where I needed a tag with a single exception. IвЂ™m not a tagger by nature, so IвЂ™m not even sure I will use tags at all. IвЂ™m curious what other people are thinking about doing.

Omnifocus 3 tags