In my project, we have a rule that automatically moves tasks and subtask to relevant sections based on a custom field. When the task/subtask is completed, they are then moved back to the “Parking lot” section and have their custom fields cleared. However, when this happens, the subtasks are un-nested, and added back again in duplicate. Is there any way to use rules to re-nest the subtasks? Manual is not an option for us.
Cheers,
@Evan_Coates You may need to separate out the rules for clearing the field and moving the task/subtask back to the Parking Lot. If this is happening all in one rule then your initial rule is probably catching the custom field before it is cleared. So, Rule 1: When task is completed, clear custom field. Rule 2: When custom field is changed to empty, move task to Parking Lot section.
Another option is to create a Done section and move completed tasks/subtasks there. Then anything occurring won’t trigger the move to the active sections.
I’m afraid this did not work for me. The nature of the project involves having the main task move to one section and then having some subtasks move to another, thus un-nesting them. but when they return to the parking lot, they are not simply discarded, their statuses can be changed again and the cycle continues.
The solution i found was an additional rule that removes tasks with a certain custom field from the project when marked complete. This re-nests subtasks, but it also allows for a scary user error where a user can accidentally mark a main task with this custom field, and then if they mark it complete, it will remove the entire task from the project, which is a huge pain. I added an additional rule to multihome all tasks removed this way to an “Archive” project to easily recover anything lost this way