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}} ===
{{Clear}}
[[Category:Android|MRO Objects == Locking ==When an (UBIK WinXMRO)]]object is locked, editing it becomes impossible. === Locked by MRO ===By design, an MRO object is locked if its parent MRO work package is confirmed. This type of locking is applied recursively to all child MRO objects. === Locked for other reasons ===There are other non-MRO reasons of locking in {{UBIK}}. If an MRO task owner or work package is locked regardless of the reasons, all its child MRO objects recursively inherit that locking state. These locking reasons include:* Locked due to [[Category:Pages with broken file linksUser_Rights|MRO Objects (UBIK WinX)user rights]];* Locked due to [[Category:WinX|MRO Objects Exclusive_Access_Content_(UBIK WinXClient)|exclusive access]].{{Version/WinXSince|4.1}}
== See also ==
* [[MRO (Plugin)]]
[[Category:Pages with broken file links|MRO Objects (UBIK WinX)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]
[[Category:Android|MRO Objects (UBIK WinX)]]
[[Category:WinX|MRO Objects (UBIK WinX)]]