==== Sequential Task ====
The [[MROCLS_SEQUENTIALTASK|sequential task classification ]] allows you to pre-define a sequence in which tasks are to be resolved by users. This means that it is required for one or multiple tasks to be finished in order for other tasks to become "unlocked" and editable. A task can have any number of "predecessors". Predecessors are the tasks that are required to be finished first.
A task can have predecessors that live anywhere else in the object hierarchy. It is not necessary for a task and its predecessors to be part of the same work package, even though this is likely the most common use case.
As a demonstration of this feature, see [[Media:Sequential_tasks_winx.mp4|this video]]. The relations between tasks are defined as in [[Media:Task_relations.png|this image]], starting at A1 and A2, which are not dependent on any other tasks. The lines (from left to right) indicate dependencies. This means that B2 has tasks A1 and A2 as its predecessors, for example.
[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:Pages with broken file links|MRO Objects (UBIK WinX)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
=== MRO objects with project information (WinX only) {{Version/WinXSince|2.5.4}} ===