{"id":13367,"date":"2017-08-29T11:06:52","date_gmt":"2017-08-29T16:06:52","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/?p=13367"},"modified":"2019-02-27T06:18:07","modified_gmt":"2019-02-27T06:18:07","slug":"vsts-update-aug-28","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/vsts-update-aug-28\/","title":{"rendered":"VSTS Update – Aug 28"},"content":{"rendered":"

This week we began rolling out our sprint 122 update for Visual Studio Team Services.\u00a0 Check out the release notes <\/a>for details.\nThere are a couple of things I want to call out.<\/p>\n

Work item rules<\/strong> – Work Item rules are the “headliner” for this sprint.\u00a0 For years and years, the way to create work item rules was by editing an XML file or using the Power Tool that was a pretty direct projection of the XML.\u00a0 This represents the beginning of the end of that.\u00a0 Now we have a new, first class rules authoring experience in the VSTS web UI.\u00a0 The rules are simple yet powerful.\u00a0 The new rules system will only be available for project with the “new” process model – sometimes called the inherited process model.\u00a0 You can tell by going into the “Process” hub under your account.\u00a0 Processes with “<\/>” next to them are the “old” process model and all the others are the new.\u00a0 The only way to get the “old” process model would have been to import a project from TFS or to hand edit XML and upload it to VSTS.\u00a0 All new projects created in VSTS only get the new process model.\u00a0 We are working on support to convert and old process template to a “new” one.\u00a0 That should be available within the next few months.\u00a0 A lot of people have been asking for a better rules experience and I really hope you like it.<\/p>\n

Forking<\/strong> – This sprint we introduced the first step towards supporting Git Forks.\u00a0 It’s just a first step but it’s enough for you to try it out and give feedback.\u00a0 For now, forks all have to be in the same account, significantly limiting the value.\u00a0 You can do much of what forks can do with branch permissions but not quite everything.\u00a0 The next “big” step will be adding support for cross account forks in a few months.\u00a0 That will really unleash the power of forks and enable you to completely decouple the work of the author from the work of the project owner.<\/p>\n

Alert filters on any field<\/strong> – From the beginning of time, work item alerts filters have only been supported for a small handful of “core” fields plus the set of fields that were modified in a work item revision.\u00a0 This sprint we have revamped our work item alert filtering system and now you can create filters on any field you choose.\u00a0 It may sound like a small thing but when you are trying to cut the noise out of your inbox, it can be crucial.\u00a0 Over the years, I’m sure I’ve had more than 100 customers complain to me about this limitation.\u00a0 I’m sooooo glad to see it lifted.<\/p>\n

Work items hub<\/strong> – We’re trying to create a new “center of gravity” for the Work hub group in VSTS.\u00a0 The backlog and boards are nice and queries are powerful but, we feel we need a better homey feeling middle ground.\u00a0 The new Work items hub will be that.\u00a0 What we released this sprint is very optimized for “my stuff in this project” – assigned to me, following, mentioned, my activity.\u00a0 It also include “recently created” – which is all work items recently created by anyone.\u00a0 The experience will feel even more complete with they yet to be released “all work items” hub that will just be a simple list of all the work items in the project in some kind of time sequence.\u00a0 I’m very interested in any feedback you have on this new experience.<\/p>\n

Profile card<\/strong> – I can’t express how excited I am about the new profile cards.\u00a0 I’ve found that, in any large org, you just don’t know everyone.\u00a0 So you stumble across some change or work item that someone did and you don’t know who they are or where they fit organizationally.\u00a0 I use contact cards in Outlook all the time to look people up and figure out where they are in the org.\u00a0 I’ve wanted a similar ability in VSTS for years.\u00a0 The new contact cards now provide that.\u00a0 They allow you to start with a person and navigate up and down the organizational hierarchy.\u00a0 We still have to surface the cards in more places but you can find them in a reasonable number of places now.\u00a0 I know it will make me more productive – no more alt-tab over to Outlook to look someone up and see what they do \ud83d\ude42<\/p>\n

Overall, it’s a pretty big sprint release and I hope you like it.<\/p>\n

Brian<\/p>\n","protected":false},"excerpt":{"rendered":"

This week we began rolling out our sprint 122 update for Visual Studio Team Services.\u00a0 Check out the release notes for details. There are a couple of things I want to call out. Work item rules – Work Item rules are the “headliner” for this sprint.\u00a0 For years and years, the way to create work […]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[9,21],"class_list":["post-13367","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-vs-team-services","tag-vsts"],"acf":[],"blog_post_summary":"

This week we began rolling out our sprint 122 update for Visual Studio Team Services.\u00a0 Check out the release notes for details. There are a couple of things I want to call out. Work item rules – Work Item rules are the “headliner” for this sprint.\u00a0 For years and years, the way to create work […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/13367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=13367"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/13367\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=13367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=13367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=13367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}