[
https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452036#comment-15452036 ]
Nicolas Malin commented on OFBIZ-7959:
--------------------------------------
Jacques I'm surprised by a getNextSeqId call out of crud or functional service. Are your sure about this ?
> Enable the status selection for WorkEffort duplication
> ------------------------------------------------------
>
> Key: OFBIZ-7959
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7959> Project: OFBiz
> Issue Type: Improvement
> Components: workeffort
> Affects Versions: Trunk
> Reporter: Montalbano Florian
> Assignee: Nicolas Malin
> Priority: Minor
> Labels: duplicate, status, workeffort
> Attachments: OFBIZ-7959.patch, OFBIZ-7959.patch
>
>
> It is possible to duplicate workeffort in the WorkEffort component (
https://localhost:8443/workeffort/control/EditWorkEffort?workEffortId=9000) but the duplicated WorkEffort keeps the same status than the original one. So when you duplicate a cancelled task, it is locked in the same state.
> We could adapt this service to allow the selection of the status for the new workeffort. Of course, you should be able to select only status that are relevant to the workeffort type.
> A first solution is to get the currentStatusId of the workeffort to duplicate. Then we can access to the linked statusTypeId. So we can retrieve all status relevant and order them by sequenceId (that way the default value is the first statuts of the sequence : created for the task).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
