A new version is available on codeplex. As I said there, it should be a 2.0 version as there are so many new features. Installation: A lot easier and faster than before. You can now install and setup the whole stuff in few minutes. An administration application let you setup the WICreator for your TFS Server, and for each Team Project you want. User experience improved: The last used Team Project is restored when launching the WICreator application. There’s now a Most Recent Used (the yellow star icon) Work Item menu item. The user can create several Work Items at once, based on predefined templates. Area Path and Iteration can now be spread among children. The hierarchy fields are automatically added to a Team Project’s Work Item Type definitions when they’re not present. Integration using Work Item: The integration process can be driven by Work Item (you have to follow the 1 changeset / 1 Work Item associated rule strictly). Integration features will be available to member of a given TFS Role. The Branch Comparison feature display for selected branches (scoped in time) what Work Items are implemented or not. The Make New Release feature enables you to merge your […]
Hi all, still alive! 🙂 It’s been a long time I didn’t blog, too many things going on in life. This is will be short. I wanted to say few things: Good job the TFS Team for the TFS 2008 Release! Especially for the GetMergeCandidates API improvement! I blogged about that in the past: in TFS 2005 it was bugged, and slow. And now I can say: "yey, it’s fast and it’s working!" Now it’s bug free: I could remove the code I’ve made in WICreator for the "Merge by Work Items" feature. Before it took around 10 minutes for one API call for two branches with lots of changesets, now it’s taking only 20 seconds! The integration people loved the TFS 2008 upgrade, I can tell you! As I said in a recent post on the WICreator Codeplex’s project, I’m starting again working on WICreator, the "Merge by Work Items" feature is pretty stable and usable now (we use it in production for at least 4 months; we did around 30 releases with it). So I’m going to make a new Codeplex release, containing this major feature, and small other ones. I’m thinking about an "administration" part for WICreator […]
A quick post to say there’s a release 1.3 of the Work Item Creator on Codeplex, the sources (including the setup) are updated and in sync with this release. I’ve added few features: 1) Now you can customize the Actions menu to specify the types of Work Item you want to create. 2) The icons corresponding to the Work Item types are now stored on the WebService so that you can add icons for your own custom Work Item types (see the "About & Setup" document about that). I also fixed few bugs. Drop me a message on Codeplex if you’re using it, I’m always interested to get some feedback!
Using the Work Item Creator to create Work Items in a hierarchical way was the first step to reach one of the goals I set myself. The Work Items are here to describe your project: – On the management side with mainly the Change Request and Bug ones. – On the development side with mainly the Task ones. What about the interaction with the Source Control? Well, when we check-in code, we associate a Task Work Item with it. The Task is owned by a Change Request or a Bug, which symbolize a feature or a fix. All the code we’re checking-in is in a "Dev" branch, whatever the iteration we’re targeting, when the development is done, it’s checked in there. Alongside with the Dev branch, we have one branch (created from the Dev on) per release of our software. So what am I so interested to do? Simply to control the creation/update of a release through the use of the Work Items! A release is done by selecting the features/fix you want it to contain through the selection of the corresponding Work Items. The Work Item Creator will analyze the changesets that belong to these features, and merge them […]
I’m pleased to announce you that the Work Item Creator and WINetwork are both available in codeplex: http://www.codeplex.com/wicreator. It’s a start, the setup process is not as easy I’d want to, but I can assure you it worth going through it! I’m waiting your feedback by email or directly in the discussion forum in Codeplex. If people are willing to help the application evolving, let me know! Concerning the Work Item Creator application, I’ve added interesting features: Siblings ordering in the hierarchy. Tree View filtering by Title content and by the following fields of a Work Item: State, Created By, Assigned To, Work Item Type. The possible values are dynamically built, I’m kinda proud of it! 🙂 The saving process was optimized.
Many people asked if there would be a release of these tools, all I can say so far is "there’s a good chance" and it may be open sourced. To release them I have to enhance things because I really do want them to be highly configurable and adaptable to your Process Template. That means I have to be able to deal with any kind of Work Item Types (as long as my three custom fields are declared), custom States, etc. We use them in production already, and if there’s a release, I want any team to be able to use them in production too. Otherwise it would be pointless… I also want both WICreator and WINetwork to be plugable. The first in-house plugin will be the creation of Work Items from JIRA Issues in WICreator and the workflow synchronization between a Work Item and its corresponding JIRA Issue in the WINetwork. The wish list for WICreator also includes: Ordered Hierarchy (almost done). A filter for the TreeView (Work Item Types, States, Owner). A "Favorites" list for the recent opened databases. Visual Studio Package instead of a standalone application? (your thought about that is welcomed) Integration with MS Project Server […]
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 to ease the communication and synchronization of Work Items. Use of the Recycle Bin. An example (in French) of a real project. I should have disabled the ClearType font antialiasing for the Video Capture, looks ugly because of it… One last thing, and not the least, if you want to know how the whole thing works internally, check out this XML file. It defines what type of Work Items we can create in respect of the hierarchy, and also describes all the Work Item Network Models I told about in this post.
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 application which allow people to create Work Items in a hierarchical way. To make the application works, all you have to do is create a "ParentWI" integer field! There are some features like the Recycle Bin one that is just cool for everyday use. As you can’t destroy a Work Item, I created a Recycle Bin one where all the Work Items people don’t need any more are stored. I also change the Area Path of the Work Item when it’s moved there, to get it out of every scope. Here what the application looks like.