It's all about the answers!

Ask a question

workitem customization


megha mittal (15112614) | asked May 06 '10, 5:39 a.m.
Hi,
I am trying to customize RTC workitems and create a new workitem type as CMVC with same attributes and workflows.
In CMVC there are certain states which are not added to workflow bases on certain component processes. example if component process is 'prototype' workitem will move from 'new-> working' .If component process is 'preship' defect will move from 'new-> design->size->review-> working '.

Now if create cmvc type workitem in RTC and assign CMVC type workflow, my problem is how to stop user from moving to 'design/size/review ' state when its component process (we can retrieve it from workitem categories which is mapped to CMVC components) doesnt allow that transition.

One possible solution is to create precondition and when user move to design state , can show him error and stop transition.
But we want something more user friendly where based on workitem categories i remove those states from workflow at run time.

I can think of two approaches,
=>One is to have multiple workflow and bind them to workitem type and based on what workitem category user selects, we load that particular workflow at runtime.
=>Another way, having only workflow and restricting state transition to that particular state .Something like a precondition which at runtime remove/disables certain states from workflow.??

4 answers



permanent link
Geoffrey Clemm (30.1k23035) | answered May 06 '10, 8:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The easiest would be approach one, i.e. to have two different work item
types, e.g. "prototype-defect" and "preship-defect". In addition to
being easy to implement, an advantage of this approach is that the end
user will not be surprised when they see different state models for the
two different kinds of defects.

Cheers,
Geoff

megham wrote:
Hi,
I am trying to customize RTC workitems and create a new workitem
type as CMVC with same attributes and workflows.
In CMVC there are certain states which are not added to workflow bases
on certain component processes. example if component process is
'prototype' workitem will move from 'new-> working' .If component
process is 'preship' defect will move from 'new-
design->size->review-> working '.

Now if create cmvc type workitem in RTC and assign CMVC type workflow,
my problem is how to stop user from moving to 'design/size/review '
state when its component process (we can retrieve it from workitem
categories which is mapped to CMVC components) doesnt allow that
transition.

One possible solution is to create precondition and when user move to
design state , can show him error and stop transition.
But we want something more user friendly where based on workitem
categories i remove those states from workflow at run time.

I can think of two approaches,
=>One is to have multiple workflow and bind them to workitem type
and based on what workitem category user selects, we load that
particular workflow at runtime.
=>Another way, having only workflow and restricting state
transition to that particular state .Something like a precondition
which at runtime remove/disables certain states from workflow.??

permanent link
megha mittal (15112614) | answered May 07 '10, 6:29 a.m.
Thanks for reply.The approach is no doubt easy one but has a problem.

We want user experience on RTC same as that of CMVC . In CMVC user selects a component(mapped to category in RTC) and create a defect . Components in CMVC have processes attached to them (preship ,prototype ,development, test etc) which get triggered once the defect is created in that component and the applicable defect states appear.

So ideally in RTC , the user should not worry about the underlying process. He create defect for a category - save it , post this RTC should take care of activating the underlying process.

Since there are lot of CMVC processess and user wont know for which category which process is active , so he wont be able to make a decision
on which work item type to choose(many choices would be confusing anyway) . So the only option is to have only one choice i.e defect and trigger the workflows based upon category.

Consider this as a case where RTC is integrated with different type so Defect management system with abstracted RTC common user interface.

So is it possible to programmatically link the workflows with workitem type defect ?

Thanks
Megha
The easiest would be approach one, i.e. to have two different work item
types, e.g. "prototype-defect" and "preship-defect". In addition to
being easy to implement, an advantage of this approach is that the end
user will not be surprised when they see different state models for the
two different kinds of defects.

Cheers,
Geoff

megham wrote:
Hi,
I am trying to customize RTC workitems and create a new workitem
type as CMVC with same attributes and workflows.
In CMVC there are certain states which are not added to workflow bases
on certain component processes. example if component process is
'prototype' workitem will move from 'new-> working' .If component
process is 'preship' defect will move from 'new-
design->size->review-> working '.

Now if create cmvc type workitem in RTC and assign CMVC type workflow,
my problem is how to stop user from moving to 'design/size/review '
state when its component process (we can retrieve it from workitem
categories which is mapped to CMVC components) doesnt allow that
transition.

One possible solution is to create precondition and when user move to
design state , can show him error and stop transition.
But we want something more user friendly where based on workitem
categories i remove those states from workflow at run time.

I can think of two approaches,
=>One is to have multiple workflow and bind them to workitem type
and based on what workitem category user selects, we load that
particular workflow at runtime.
=>Another way, having only workflow and restricting state
transition to that particular state .Something like a precondition
which at runtime remove/disables certain states from workflow.??

permanent link
Geoffrey Clemm (30.1k23035) | answered May 07 '10, 8:31 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The association of a work item type to a workflow is done at the project
area level, not separately per category. But I agree that allowing the
workflow to depend on the assigned category would be a nice feature ...
I've submitted work item 114141 for it.

Cheers,
Geoff

megham wrote:
Thanks for reply.The approach is no doubt easy one but has a problem.

We want user experience on RTC same as that of CMVC . In CMVC user
selects a component(mapped to category in RTC) and create a defect .
Components in CMVC have processes attached to them (preship
,prototype ,development, test etc) which get triggered once the
defect is created in that component and the applicable defect states
appear.

So ideally in RTC , the user should not worry about the underlying
process. He create defect for a category - save it , post this RTC
should take care of activating the underlying process.

Since there are lot of CMVC processess and user wont know for which
category which process is active , so he wont be able to make a
decision
on which work item type to choose(many choices would be confusing
anyway) . So the only option is to have only one choice i.e defect
and trigger the workflows based upon category.

Consider this as a case where RTC is integrated with different type so
Defect management system with abstracted RTC common user interface.

So is it possible to programmatically link the workflows with workitem
type defect ?

Thanks
Megha
gmclemmwrote:
The easiest would be approach one, i.e. to have two different work
item
types, e.g. "prototype-defect" and
"preship-defect". In addition to
being easy to implement, an advantage of this approach is that the
end
user will not be surprised when they see different state models for
the
two different kinds of defects.

Cheers,
Geoff

megham wrote:
Hi,
I am trying to customize RTC workitems and create a new workitem
type as CMVC with same attributes and workflows.
In CMVC there are certain states which are not added to workflow
bases
on certain component processes. example if component process is
'prototype' workitem will move from 'new-> working' .If
component
process is 'preship' defect will move from 'new-
design->size->review-> working '.

Now if create cmvc type workitem in RTC and assign CMVC type
workflow,
my problem is how to stop user from moving to 'design/size/review '
state when its component process (we can retrieve it from workitem
categories which is mapped to CMVC components) doesnt allow that
transition.

One possible solution is to create precondition and when user move
to
design state , can show him error and stop transition.
But we want something more user friendly where based on workitem
categories i remove those states from workflow at run time.

I can think of two approaches,
=>One is to have multiple workflow and bind them to workitem
type
and based on what workitem category user selects, we load that
particular workflow at runtime.
=>Another way, having only workflow and restricting state
transition to that particular state .Something like a precondition
which at runtime remove/disables certain states from workflow.??


permanent link
megha mittal (15112614) | answered May 11 '10, 1:44 a.m.
Thanks .But i need a workaround for the time being to deal with my problem.If i cannot handle workflow can i take care of workitem states and transition separately at runtime by enabling/disabling them based on workitem category through some precondition ?
eg if category is "xyz" remove " verify" state and transition from "working" to " verify" instead show transition from " working" to " close".
As i told earlier i have written precondition which stops user from doing this transition and it will display error message on " save" but i dont want to sow error instead remove "not supported" state from workflow at the time of that "save" operation.

The association of a work item type to a workflow is done at the project
area level, not separately per category. But I agree that allowing the
workflow to depend on the assigned category would be a nice feature ...
I've submitted work item 114141 for it.

Cheers,
Geoff

megham wrote:
Thanks for reply.The approach is no doubt easy one but has a problem.

We want user experience on RTC same as that of CMVC . In CMVC user
selects a component(mapped to category in RTC) and create a defect .
Components in CMVC have processes attached to them (preship
,prototype ,development, test etc) which get triggered once the
defect is created in that component and the applicable defect states
appear.

So ideally in RTC , the user should not worry about the underlying
process. He create defect for a category - save it , post this RTC
should take care of activating the underlying process.

Since there are lot of CMVC processess and user wont know for which
category which process is active , so he wont be able to make a
decision
on which work item type to choose(many choices would be confusing
anyway) . So the only option is to have only one choice i.e defect
and trigger the workflows based upon category.

Consider this as a case where RTC is integrated with different type so
Defect management system with abstracted RTC common user interface.

So is it possible to programmatically link the workflows with workitem
type defect ?

Thanks
Megha
gmclemmwrote:
The easiest would be approach one, i.e. to have two different work
item
types, e.g. "prototype-defect" and
"preship-defect". In addition to
being easy to implement, an advantage of this approach is that the
end
user will not be surprised when they see different state models for
the
two different kinds of defects.

Cheers,
Geoff

megham wrote:
Hi,
I am trying to customize RTC workitems and create a new workitem
type as CMVC with same attributes and workflows.
In CMVC there are certain states which are not added to workflow
bases
on certain component processes. example if component process is
'prototype' workitem will move from 'new-> working' .If
component
process is 'preship' defect will move from 'new-
design->size->review-> working '.

Now if create cmvc type workitem in RTC and assign CMVC type
workflow,
my problem is how to stop user from moving to 'design/size/review '
state when its component process (we can retrieve it from workitem
categories which is mapped to CMVC components) doesnt allow that
transition.

One possible solution is to create precondition and when user move
to
design state , can show him error and stop transition.
But we want something more user friendly where based on workitem
categories i remove those states from workflow at run time.

I can think of two approaches,
=>One is to have multiple workflow and bind them to workitem
type
and based on what workitem category user selects, we load that
particular workflow at runtime.
=>Another way, having only workflow and restricting state
transition to that particular state .Something like a precondition
which at runtime remove/disables certain states from workflow.??

Your answer


Register or to post your answer.