precedes
Description: The TaskJuggler Manual
Keywords: taskjuggler, project, management

### The TaskJuggler User Manual

Project Management beyond Gantt Chart Drawing

<< persistent << | Table Of Contents | >> priority >>

Keyword | precedes

Purpose | Specifies that the tasks with the specified IDs cannot start before the task has been finished. If multiple IDs are specified, they must be separated by commas. IDs must be either global or relative. A relative ID starts with a number of '!'. Each '!' moves the scope to the parent task. Global IDs do not contain '!', but have IDs separated by dots. By using the 'precedes' attribute, the scheduling policy is automatically set to alap. If both depends and precedes are used within a task, the last policy counts.
Syntax | `precedes (<ABSOLUTE ID> | <ID> | <RELATIVE ID>) [{ <attributes> }] [, (<ABSOLUTE ID> | <ID> | <RELATIVE ID>) [[, ... ]]...]`
Arguments | ABSOLUTE ID [ABSOLUTE_ID] | A reference using the full qualified ID of a task. The IDs of all enclosing parent tasks must be prepended to the task ID and separated with a dot, e.g. `proj.plan.doc`.
ID | Just the ID of the task without and parent IDs.
RELATIVE ID | A relative task ID always starts with one or more exclamation marks and is followed by a task ID. Each exclamation mark lifts the scope where the ID is looked for to the enclosing task. The ID may contain some of the parent IDs separated by dots, e. g. `!!plan.doc`.
Context | task, supplement (task)

Attributes | gapduration, gaplength, onend, onstart

<< persistent << | Table Of Contents | >> priority >>

Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 by Chris Schlaeger <chris@linux.com>.TaskJuggler is a trademark of Chris Schlaeger.