It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×12,010

question asked: Jun 13 '13, 7:54 a.m.
question was seen: 4,469 times
last updated: Jun 13 '13, 11:40 a.m.

Related questions

Why does a Task become state "Invalid" when moved to stategroup "Closed" in Taskboard after adding a new state and action to Epic?

0
Guido Schneider (3.4k●14●91●115) | asked Jun 13 '13, 7:54 a.m.
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.

Accepted answer

0
permanent link
Kot T. (1.5k●1●13●19) | answered Jun 13 '13, 9:28 a.m.
JAZZ DEVELOPER
Hi Guido,
There is the following technote related to your finding above ==> http://www-01.ibm.com/support/docview.wss?uid=swg21584382
Guido Schneider selected this answer as the correct answer
Comments
Guido Schneider commented Jun 13 '13, 9:41 a.m.

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.

Guido Schneider commented Jun 13 '13, 9:47 a.m.

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

Kot T. commented Jun 13 '13, 11:40 a.m.
JAZZ DEVELOPER

Hi Guido, I am not aware of any defect for this technote.

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Guido Schneider (3.4k●14●91●115) | answered Jun 13 '13, 7:54 a.m.
edited Jun 13 '13, 7:55 a.m.
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: 
    <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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.