Skip to main content
Question

Incompleted Work Assignment 'time to completion' to zero

  • February 17, 2026
  • 3 replies
  • 19 views
Wendy J
Do Gooder (Customer)
Forum|alt.badge.img

Since changing to 24R2 and SU14-19  any work tasks that have previously had an incompleted work assignment are not closing on completion of the final assignment. The MWO user closes the task and there is no further work to be completed, however the work task retains all the closing information but NOT the actual finish date and the task remains at work started. This is due to the time to completion field having a value on the Incompleted assignment. Prior to the update, no value was stored here and work tasks changed to Work Done automatically. IFS thinks there is still outstanding time on the task.

It now requires manual intervention to close these tasks down.

Is there a way to stop the time to completion field being populated? The engineer cannot set this to zero on MWO and I cant find a way to delete the time to completion field in the Assignment.

We do not use the direct allocations method to send work to device. Assign work or PSO scheduling.

Any advice on how we can work around this would be appreciated as this is causing high levels on manual closures for our back office teams.

Thank you

 

 

3 replies

A
Superhero (Employee)
  • anmise
  • Superhero (Employee)
  • February 17, 2026

Hi  ​@Wendy J 

it should be possible to set “Time to Complete” to 0, so please log a support case. I think you can argue that if the time to complete is 0, the work should be set to work done, assuming there is no remaining demand to fulfil. 

I’m curious to understand why you’re using the incomplete status, if no work remains on the task (given you’re looking to set it to done). Is it just for reporting clarity, clearly distinguishing between work that was in fact fully completed and work that we may have been interrupted or stopped before the full scope of work was delivered?

Wendy J
Do Gooder (Customer)
Forum|alt.badge.img
  • Wendy J
  • Author
  • Do Gooder (Customer)
  • February 17, 2026

Hi ​@anmise,

Thank you for your responding. We have a support case open and have been advised that this is the functionality. 

See comment:

The only scenario in which the Work Task would automatically transition to Work Done is when the remaining time to completion is set to 0 and all other associated work assignments are completed. In your case, since the remaining time value (0.9) is already populated and cannot be amended, the system will not automatically complete the task. As a result, users would need to manually set the Work Task to Work Done.

This never caused us an issue prior to the SU we deployed in August 2025 and since then we have seen new behaviour.

The scenario we have is that Assignment 1 is returned as Incomplete by the MWO user for back office intervention or parts are ordered and a time to completion is recorded against that assignment.

When the task is ready to schedule back to an engineer, the subsequent Assignment 2 is created by IFS or manually assigned and completed on MWO and closed fully complete. The Assignment 2 status is set to Complete with 0 time to complete. The performed work and performed action fields are populated, however the Actual Finish date does not record in the required field and the status does not change to Work Done. Because there is a time to complete on the previous assignment the task will not close.

We are manually adding the actual finish date and changing the status to close the tasks.

I assumed that if the last Assignment was Complete and had zero time remaining, this should signify that the task can be closed as Work Done. Any advice is much appreciated.

A
Superhero (Employee)
  • anmise
  • Superhero (Employee)
  • February 17, 2026

​@Wendy J 

since you cannot set the “Time to Completion” to 0 in mWO because of a client validation (you can in web client), you cannot achieve the pre-requisites to have the work task set to work done, which I’d argue is a clear cut defect. 

Reading the support response very literally, they are also suggesting that if you have any assignments in statuses other than completed (i.e. incomplete), that it won’t set it to work done. 

And if any assignments have a “Time to Completion” >0, you could never automatically set it to Work Done.

So the logic is basically that a Work Task is automatically transitioned to Work Done only if all work assignments are completed, and the sum of remaining Time to Completion = 0, which can never happen if you’ve incompleted an assignment with a time to complete before.

I might be missing something here, but I’d argue that if you have one or many assignments in status incomplete but a single assignment with status complete, the work task status should be set to Work Done.

 

Terms & ConditionsCookie settingsAccessibility statement