VSTS Work Item Rules

Sign in to queue

Description

In this episode, Donovan is joined by Charles Taylor, to show the Visual Studio Team Services Work Item Rules. Using these rules, you can customize the behavior of your work items in VSTS.

Embed

Download

Download this episode

Download captions

The Discussion

  • User profile image
    Arad

    You guys probably forgot to upload the edited version of the video! :)

  • User profile image
    lef

    Are you planning to support rules across different items? Example: a developer could not have two distinct tasks in parallel at the same time. Or: setting a story to "done" when all its tasks are done.

  • User profile image
    rogreen

    @Arad: Thanks for pointing that out to us. We made the edit and republished. 

  • User profile image
    Steve

    Looks great - are we going to see this in TFS 2017 or 2018?

    Manual edits of XML are a real pain, this makes the processes so much easier.

  • User profile image
    nmenegay

    Great questions Donovan! [H]

    By the way, this nice UI is only available to inherited processes, correct?

  • User profile image
    charlestayl​or

    @nmenegay: Yes! For now, the new Work Item Rules UI is only available for those on VSTS using the inheritance process model for process customization. 

    Thanks, 

    Charles Taylor

  • User profile image
    charlestayl​or

    @lef: Thanks for the feedback! We have definitely heard the request for the ability to achieve more powerful scenarios with the new Work Item Rules experience. We do not have definitive plans to tackle those scenarios you mentioned, but they are on our backlog. And as I mentioned, this is definitely not something we are walking away from. We want to continue improving the experience and making it more robust. 

    Thanks, 

    Charles Taylor

     

  • User profile image
    charlestayl​or

    @Steve: Thanks for the feedback! Unfortunately, this new Work Item Rules UI is only available on VSTS. Currently, while the new UI is powerful, it does not support all possible rule configurations supported via XML with TFS. As such, we have not made definitive plans to bring this experience to TFS.

    In the meantime, we are continuing to invest in the UI and build out added experiences to fill some of these gaps.

    Thanks,

    Charles Taylor 

  • User profile image
    David_Lean

    Nice. This will be handy.

    That said, there is/was much value in VSTS creating the "Best Practise" template that works for most people. So many teams create customisations & processes that actually slow them down. (eg: Changes that kept one guy happy who thought it was a good idea, but now he has left the team ;)  )

  • User profile image
    Donovan

    @David_Lean: I could not agree more. As I said in the video I hope people don't go crazy with this. When I was a consultant I spent a lot of my time talking customers out of customizing the template. Take the time to really learn why the template is the way it is before you change it.

    Ask yourself why are we moving from where we are now to VSTS? The answer normally is because the tool/process you have today is lacking. So why customize VSTS back to the tool you are leaving?

    The out of the box process templates are great and have been shaped over a long period of time. They have best practices and years of team experiences baked in.

    After sitting with a customer and understanding why the made the customization I realized what they wanted was already in the template they just did not know how to use it. 

    Here you can read how each process was designed to be used https://docs.microsoft.com/en-us/vsts/work/work-items/guidance/choose-process

Add Your 2 Cents