News about WICreator and WINetwork
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 (in my dreams or at least in a not so near future): linking a Work Item with a MS Project Task, being able to update the task from a Work Item. No more Project Web Access for timesheet updates!
Stay tuned!
Posted by
at
23:54:48
Hi Loic, this concept of creating an hierarchy is quite interesting. We are trying to create something similar in my company to manage a feature-task relationship. Have you had a chance to put in practice some of these concepts in reporting ?. I mean, do you know if the hierarchy will work fine when you populate the warehouse data ?.
Thanks, a congratulations for this amazing work.
cibrax,
Well, these are still Work Items, so existing Reports like Remaining Work, Project Velocity, Bugs, etc. will work, but in a flat way…
I’m not sure to understand what you’d really like to bring in reports thanks to the hierarchy.
For me, hierarchy is not a substitution to Area Path, so we still can focus our report on a given part of the project.
I understand your point of view. Supose you have a Feature Work item (I do not want to use an area here, because I can not link information to it) with some child items representing the development tasks, and I want to generate a report to know the work status per feature, I do not, 50% of the work items in the feature 1 are complete, other 30% are in progress, etc. In that case, the hierarchy is very helpful.
Thanks
Pablo.
Bonjour Loic, pourrais-tu me contacter par mail au sujet de ce projet.
Merci.
Sébastien FERRAND
Microsoft Visual C# MVP
Top interesting staff. I’m just in the beginning of deploying the TS as for the project life cycle (after deploying it fully for Source contol and CI builds).
I may try your app - so wait for feedback later.
By the way - 5 days ago “Project Server 2007 VSTS Connector” was released on CodePlex. give it a look as I think it is something you looked for.
See also my project on codePlex: “TFS Follow Branch History Add-in for VS”
very good!
Know that feeling all too well!
re-read this latest entry. i think it’s seriously time to throw in the towell.