Why does a Task become state "Invalid" when moved to stategroup "Closed" in Taskboard after adding a new state and action to Epic?
We added with the RTC Eclipse V.4.0.2 a new State to a Plan Item (Epic) and also a new action (failed).
After doing this we observed, that in the RTC "Taskboard", a task moved from "In Progress" stategroup to the "Closed" stategroup, get's the State "Invalid" instead of "Done".
It's quite strange that adding a State to Epic has an influence of moving a task in the Taskboard.
This behaviour is severe, because the user will not see this wrong state.
After doing this we observed, that in the RTC "Taskboard", a task moved from "In Progress" stategroup to the "Closed" stategroup, get's the State "Invalid" instead of "Done".
It's quite strange that adding a State to Epic has an influence of moving a task in the Taskboard.
This behaviour is severe, because the user will not see this wrong state.
Accepted answer
Hi Guido,
There is the following technote related to your finding above ==> http://www-01.ibm.com/support/docview.wss?uid=swg21584382
There is the following technote related to your finding above ==> http://www-01.ibm.com/support/docview.wss?uid=swg21584382
Comments
Your absolutly right.
But why is such a sever issue not solved between 3.0 and 4.0.3. This is unbelivable. We have now 100'ts of workitems in wrong state and have to find out which WI in which Project Areas.
I'm realy upset.
BTW: Do you know the related defect for the Technote? Hope there is one and not just this technote.
I have opened a new one:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=268959
Hi Guido, I am not aware of any defect for this technote.
One other answer
After analyzing the differences in the process XML we recognized, that the save operation of RTC Eclipse has changed the order of all <action> elements within a <workflow> element for all <workflowDefinition>.
Working:
After changing this order in the XML the problem was solved.
I will write a defect, because it cannot be that a simple save in the Eclipse Process editor changes the behaviour of the taskboard.
It's also not nice, that the taskboard is related to an order of XML elements in the process definition.
Working:
<workflow description="Workflow used for Tasks" name="Process BT: Task" reopenActionId="com.siemens.btq.task.action.a5" resolveActionId="com.siemens.btq.task.action.a3" startActionId="com.siemens.btq.task.action.a1">
<action icon="processattachment:/workflow/resolve.gif" id="com.siemens.btq.task.action.a3" name="Set Done" state="com.siemens.btq.task.state.s1"/>
<action icon="processattachment:/workflow/inprogress.gif" id="com.siemens.btq.task.action.a2" name="Start Working" state="com.siemens.btq.task.state.s2"/>
<action icon="processattachment:/workflow/open.gif" id="com.siemens.btq.task.action.a1" name="Initialize" state="com.siemens.btq.task.state.s4"/>
<action icon="processattachment:/workflow/reject.gif" id="com.siemens.btq.task.action.a7" name="Set Obsolete" state="com.siemens.btq.task.state.s5"/>
<action icon="processattachment:/workflow/open.gif" id="com.siemens.btq.task.action.a6" name="Stop Working" state="com.siemens.btq.task.state.s4"/>
<action icon="processattachment:/workflow/reopen.gif" id="com.siemens.btq.task.action.a5" name="Reopen" state="com.siemens.btq.task.state.s4"/>
:
:
</workflow>
Not working:
<workflow description="Workflow used for Tasks" name="Process BT: Task" reopenActionId="com.siemens.btq.task.action.a5" resolveActionId="com.siemens.btq.task.action.a3" startActionId="com.siemens.btq.task.action.a1">
<action icon="processattachment:/workflow/reopen.gif" id="com.siemens.btq.task.action.a5" name="Reopen" state="com.siemens.btq.task.state.s4"/>
<action icon="processattachment:/workflow/open.gif" id="com.siemens.btq.task.action.a6" name="Stop Working" state="com.siemens.btq.task.state.s4"/>
<action icon="processattachment:/workflow/reject.gif" id="com.siemens.btq.task.action.a7" name="Set Obsolete" state="com.siemens.btq.task.state.s5"/>
<action icon="processattachment:/workflow/open.gif" id="com.siemens.btq.task.action.a1" name="Initialize" state="com.siemens.btq.task.state.s4"/>
<action icon="processattachment:/workflow/inprogress.gif" id="com.siemens.btq.task.action.a2" name="Start Working" state="com.siemens.btq.task.state.s2"/>
<action icon="processattachment:/workflow/resolve.gif" id="com.siemens.btq.task.action.a3" name="Set Done" state="com.siemens.btq.task.state.s1"/>
:
:
</workflow>
After changing this order in the XML the problem was solved.
I will write a defect, because it cannot be that a simple save in the Eclipse Process editor changes the behaviour of the taskboard.
It's also not nice, that the taskboard is related to an order of XML elements in the process definition.