Partilhar via

Frustrated with the WIT Rules Engine?

  • Artigo

I use TFS to manage my software projects. The software projects are to develop TFS, which gets kind of wierd :-)

But there are many things I'd like to do with the WIT Rules engine, that I can't. Like

  • You can't mark at task as Closed, unless you have Remaining Hours set to zero.
  • You can't mark a bug as closed, unless all dependent bugs are also marked closed (same with tasks)
  • If you mark a bug a duplicate of another bug, you must link to that bug.

These are just a few. (I could go on and on)

We are looking into how we can make the rules engine more extensible and flexible. But I want to make sure it meets your needs.

So, let me know ... what is that that YOU want to do with the rules engine, but can't?

Comments

  • Anonymous
    March 01, 2007
    Gregg, I'd recommend making the WIT "rules" TFS admin configurable on a project by project basis in Rosario. This will allow the TFS admin to customize the rules to fit the development team's (or development manager's) work style for each project. Every dev team I've worked with (developing or managing) has worked differently and no pre-configured set of WIT rules seems to exactly fit. Jeff Lynch

  • Anonymous
    March 01, 2007
    Any chance of seeing workflow (WF) be part of TFS?

  • Anonymous
    March 01, 2007
    Adding diferent access control for different work item states. For example if you create an approval work item it can be edited up until the time it is marked as approved.

  • Anonymous
    March 01, 2007
    Gregg, things I'd like to see in a future version:

  • custom form layouts for different user groups, e.g. our support team should only see support related fields
  • New linktype: Links to child workitems. The work for our scenrios is done in several (child) development tasks. It should be possible to define a rule to prevent a workitem of being set to resolved if one of the child items is not resolved. I kow you already said that, but it is my main requirement for the rules engine.
  • automatically set a workitem to resolved if all child workitems are resolved.
  • The possibility to make controls invisible based on a rule. Regards, Stefan

  • Anonymous
    March 03, 2007
    Sometimes I feel a little like I'm sitting at an information desk in a mall directing people to what

  • Anonymous
    March 03, 2007
    Sometimes I feel a little like I'm sitting at an information desk in a mall directing people to what

  • Anonymous
    March 05, 2007
    These are great comments. Thanks for taking the time. Please keep them coming.

  • Anonymous
    March 07, 2007
    The comment has been removed

  • Anonymous
    March 18, 2007
    The comment has been removed

  • Anonymous
    March 18, 2007
    The comment has been removed

  • Anonymous
    March 19, 2007
    Gregg, one more thing: I'd like to have a transition rule which only fires depending on a field value. E.g.: We have a custom workitem field. For the transition from active to resolved it should be "required" but only if the reason is "fixed". If the bug is deffered it should not be required. Another example: we have an extra field "blocked reason". This should be required if you set the issue field to yes. regards, Stefan

  • Anonymous
    March 23, 2007
    This is amazing information. Lots of it we already knew about, but it adds such clarity to have examples. Thanks!