Editing a Parent Task Status with Fusion | Community
Skip to main content
KellieGardner
Community Advisor
KellieGardnerCommunity Advisor
Community Advisor
February 26, 2026
Question

Editing a Parent Task Status with Fusion

  • February 26, 2026
  • 1 reply
  • 12 views

We have a workflow that incorporates multiple rounds of reviews as tasks. We are trying to automate the closure of these tasks when rounds aren’t needed and approvals are obtained earlier than what we planned for.

 

What I’m struggling with is the Parent Task status.

 

Since the projects are set for the parent tasks to be a summary of the child tasks, when the child tasks are closed (status of not needed which equates with complete) the parent task is updated to Complete, which is ultimately fine but not the preference. We’d like it to update to “not needed,” which equates with Complete.

 

Is there a way to edit this task status via Fusion? I’ve tried with a basic scenario without success, but not sure if there is any other option.

 

 

1 reply

KatherineLa
Community Advisor
KatherineLaCommunity Advisor
Community Advisor
February 27, 2026

The switch to Complete happens because the Project Settings are ‘Automatic’ for ‘Summary Completion Mode’. As far as I know, there’s no way to override that, even with Fusion. Usually if the UI won’t allow you to do something, Fusion respects the same logic. Switching the Summary Completion Mode setting to Manual would permit that update, but that applies to the entire project which might not be ideal either. 

 

If the long-range goal is to be able to analyze that data after a project is fully closed though, there’s some trickery you could do as part of the project’s closure. If I needed to retain the normal auto-close procedure during the life cycle of the project, and just wanted the data accurate for metrics after, then I’d leverage Fusion.

 

Set a scenario to detect the change of a project’s status to Closed, THEN have it update that Summary Completion Mode setting to Manual. Once it was flipped, the scenario could then be told to iterate through all the tasks and isolate any parent task where the children were ‘Not Needed’ to make the update. I’ve never tried that update on a closed project though. If it gave an error about changes to a closed project, you might have to tell it to re-open the project, make the changes and close it again.

 

Whether it’s worth designing is a judgement call on how useful being able to look back and count the number of ‘Not Needed’ rounds was overall to your metrics, and if this could create confusion with the PM team if projects get re-opened. 

Terms & ConditionsAccessibility statement

Loading footer...