[
https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451841#comment-15451841 ]
Jacques Le Roux commented on OFBIZ-7959:
----------------------------------------
Hi Florian,
I suggest this in EditWorkEffortDup
{code}
[... ]
<set field="newWorkEffortId" value="${groovy: delegator.getNextSeqIdLong('WorkEffort')}"/>
[... ]
<field name="newWorkEffortId" parameter-name="workEffortId" tooltip="${uiLabelMap.ProductDuplicateRemoveSelectedWithNewId}"><text size="20" maxlength="20"></text></field>
[... ]
{code}
The user can still force the Id to the value he wants, we just suggest the next possible automated Id
> 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
