Is programmatic approcatch for customizing work item right?
I'm developing visualizing tool for jazz team server with client library.
I had to add custom attributes and custom worktype into team repository. So, first, I used the process template with customized attributes and workitem type. Next, I used programmatic approach which use with IWorkItemCommn API on Express-C.
I thought that customizing workitem couldn't be done without standard server license. It was good for me. So I stopped importing customized process template.
I'd like to customize workitem with programmatic approach on Client Library. But I'm scared that jazz team may stop providing the API of customizing workitem attribute and type on Express-C or without sever license.
Is it right to customize workitem types and attributes with client library on any team repository?
best regards,
-Takeshi
I had to add custom attributes and custom worktype into team repository. So, first, I used the process template with customized attributes and workitem type. Next, I used programmatic approach which use with IWorkItemCommn API on Express-C.
I thought that customizing workitem couldn't be done without standard server license. It was good for me. So I stopped importing customized process template.
I'd like to customize workitem with programmatic approach on Client Library. But I'm scared that jazz team may stop providing the API of customizing workitem attribute and type on Express-C or without sever license.
Is it right to customize workitem types and attributes with client library on any team repository?
best regards,
-Takeshi
One answer
Your tool should never require the existence of a certain work item type
or certain custom attributes to be functional. If is does you might want
to rethink your approach.
You are right that also the programmatic creation of work item types
(which your tool should not do - see above) is subject to license
control. I.e. it might be possible on certain editions and impossible on
others.
Kai
Jazz Process team
changevision wrote:
or certain custom attributes to be functional. If is does you might want
to rethink your approach.
You are right that also the programmatic creation of work item types
(which your tool should not do - see above) is subject to license
control. I.e. it might be possible on certain editions and impossible on
others.
Kai
Jazz Process team
changevision wrote:
I'm developing visualizing tool for jazz team server with client
library.
I had to add custom attributes and custom worktype into team
repository. So, first, I used the process template with customized
attributes and workitem type. Next, I used programmatic approach
which use with IWorkItemCommn API on Express-C.
I thought that customizing workitem couldn't be done without standard
server license. It was good for me. So I stopped importing customized
process template.
I'd like to customize workitem with programmatic approach on Client
Library. But I'm scared that jazz team may stop providing the API of
customizing workitem attribute and type on Express-C or without sever
license.
Is it right to customize workitem types and attributes with client
library on any team repository?
best regards,
-Takeshi