There are two ways you can do this. If you always need the grandparent information you can add a second parent to a column. So select a key field from the parent information in standard mode and convert to text mode. So here is the parent:name field converted to text mode: valuefield=parent:name querysort=parent:name valueformat=HTML displayname= linkedname=parent namekey=view.relatedcolumn namekeyargkey.0=parent namekeyargkey.1=name And add a second parent valuefield=parent:parent:name querysort=parent:parent:name valueformat=HTML displayname=Grandparent namekey=view.relatedcolumn namekeyargkey.0=parent namekeyargkey.1=parent namekeyargkey.2=name For a filter the process is similar: parent:name=Grand parent:name_Mod=cicontains Becomes parent:parent:name=Grand parent:parent:name_Mod=cicontains For the above to work you should have a filter that indent > 1 to prevent the system from trying to find grandparent information on tasks without grandparents. If you sometimes need parent information and sometimes need the information in the current task. Add a calculated field called say "Parent Chase" to all tasks with 2 different forms. For the parent task the "Parent Chase" field has a formula that is equal to a key field like name. For the child tasks, the field is equal to parent.Parent Chase. For grandchild tasks, their parent already has the field to it's parent field so this will work for fields all the way down. You will have to recalculate fields a few times if you have deep sub-task trees. -- Melinda Layten, Senior Consultant Work Management Improvement CapabilitySource Phone: (484) 505-6855 site:
www.capabilitysource.com email: melinda.layten@capabilitysource.com Helpful? Buy me a coffee:
https://www.patreon.com/mlayten - we simplify your work so you can run your business -
