Browse by Tags
All Tags »
WIT (
RSS)
Working with many clients on ALM and development processes I am often in a situation like this: I create a Process Template for the client and then create a Team Project based on it. The Team Project will become the "reference Team Project"...
I'm in the process of easing the installation of the Work Item Creator. To do that, I wanted to detect in runtime if a given Team Project doesn’t have its Work Item Types (WITs) supporting hierarchy and then asking the user to add them. It’s...
My team came up with a request that looked at first « easy to code » but which turned out to be a real pain: managing order in siblings. As I wrote in a previous post , I was using the Work Item's Links (to link a son with its father)...
I've made some videos of the WICreator application, used with the WINetwork system. Check them out, I think they worth it! This one is about the creation of a project and the realization of a task with a code review. Both processes use the WINetwork...
Yes I know, spare me with the poor naming of this application, this is what happens when you allow yourself no more than 30sec to find something... Anyway, as I told in previous posts, hierarchy in Work Items are a must for us, so we had to develop an...
Now we have hierarchy in our Work Item, we can take things to another level. The Hierarchy implies a relation between these Work Items, so it is natural to think that when one's is evolving, it impacts its surroundings. For instance, you have a Change...
There're few things I want to share about the WorkItemStore::GetWorkItem() method. First, it may sound clear for everybody, but: WorkItem a = wis . GetWorkItem ( 10 ); WorkItem b = wis . GetWorkItem ( 10 ); The instance a and b won’t be the...
Create a custom field in all your concerned Work Items named "ParentWI" for instance, of type integer. Now, say you want to link two Work Items, the method will looks like: public void LinkWorkItems ( WorkItem parent , WorkItem son ) { RelatedLink...
Relationship between Work Items is something important to me. The first thing that is obviously missing is a sense of hierarchy. Hierarchy is everywhere in life, so it is in a project management. Of course you can live without this notion in Team System...
The development team I'm working on moved to Team System in September 2006. The shift from what we used before was pretty huge, mainly because we weren't using SCM at all ("WinMerge rulez!" you may say). Of course, things had to evolve...