Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ofbiz.apache.org
Date: Sat, 17 Sep 2016 13:41:20 +0000 (UTC)
From: "Nicolas Malin (JIRA)" <jira@apache.org>
To: notifications@ofbiz.apache.org
Message-ID: <JIRA.12998145.1471512285000.596678.1474119680528@Atlassian.JIRA>
In-Reply-To: <JIRA.12998145.1471512285000@Atlassian.JIRA>
References: <JIRA.12998145.1471512285000@Atlassian.JIRA> <JIRA.12998145.1471512285735@arcas>
Subject: [jira] [Closed] (OFBIZ-7959) Enable the status selection for
 WorkEffort duplication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 17 Sep 2016 13:41:22 -0000


     [ https://issues.apache.org/jira/browse/OFBIZ-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Malin closed OFBIZ-7959.
--------------------------------
       Resolution: Implemented
    Fix Version/s: Upcoming Branch

Ok Florient, your submission is on trunk at revision 1761233.

I realize some correction :
 * remove modification to load status from Scrum et Project, simply because it's not datas core. If we want set this drop-down dynamical we need to improve the status resolution by a statusType tree.
 * remove tooltip on newWorkEffortId field because is not corresponding to the situation ;)
 * add label for field newWorkEffortId

I'm not agree to keep newWorkEffortId field because it's potential risk for the automatic system to have an advertise user that when hurt it. But it's already present on ftl and if we really want remove it, we can open a new issue

> 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
>             Fix For: Upcoming Branch
>
>         Attachments: OFBIZ-7959.patch, 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)