[
https://issues.apache.org/jira/browse/OFBIZ-6934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244237#comment-15244237
]
Pierre Smits commented on OFBIZ-6934:
-------------------------------------
Maybe current behaviour is fine for you, but is it for Resource Planners?
In current code base setting the estitmatedCompletionDate is optional. But
assignment of a fixed asset to a WorkEffort is not supposed to be undetermined
(regarding the end date) as it would not work for planning (and utilisation
reports). We have to keep in mind that estimatedCompletionDate is not the same
as actualCompletionDate. The first is intent/plan/target, the second is
actuals/reality.
So, we could
# make setting the thruDate a required field, or
# provide the service that, when the truDate of the fixed asset assigned is not
set explicitly, uses the end date (estimated) of the task as the intended
thruDate of the assigned fixed asset.
IMO, the latter would produce a better UX for the production run manager as
he/she has less actions to execute.
> Assigning a fixed asset to a WorkEffort record doesn't respect the thruDate
> of the WorkEffort
> ---------------------------------------------------------------------------------------------
>
> Key: OFBIZ-6934
> URL: https://issues.apache.org/jira/browse/OFBIZ-6934
> Project: OFBiz
> Issue Type: Bug
> Components: workeffort
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Mridul Pathak
>
> When a fixed asset is assigned to a workeffort record the service should set
> the thruDate (estimatedCompletionDate) on the assignment. However this
> doesn't happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
