{"id":3131,"date":"2012-06-26T06:00:00","date_gmt":"2012-06-26T06:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2012\/06\/26\/team-foundation-services-updates-626\/"},"modified":"2024-05-02T14:00:44","modified_gmt":"2024-05-02T21:00:44","slug":"team-foundation-services-updates-626","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/team-foundation-services-updates-626\/","title":{"rendered":"Team Foundation Services Updates 6\/26"},"content":{"rendered":"

Well, the last 3 weeks were busy.\u00a0 We announced our Azure Continuous Deployment support and removed the invitation codes to open the service up to everyone.\u00a0 As I wrote in my Spring wrap up post<\/a>, we\u2019ve kind of emptied the pipeline of all of the big stuff we\u2019ve had in progress.\u00a0 So this sprint, we\u2019ve got a few nice little enhancements to the service but nothing that\u2019s going to change your life or blow your socks off.\u00a0 This is the denouement after the climax \"Image<\/a>\u00a0 We\u2019re building a new pipeline now but it\u2019s probably going to be fairly tame for a couple of sprints.\u00a0 Let\u2019s not forget that we still have to tie the bow on TFS 2012 so there\u2019s not a lack of things to keep us busy.<\/p>\n

The changes you might notice in this sprint include:<\/p>\n

Next\/Previous Buttons on the work item form<\/strong> \u2013 We\u2019ve gradually been chipping away at some work item tracking usability improvements.\u00a0 In my post on the 6\/4 service update<\/a> I described the addition of next\/prev buttons to the triage view.\u00a0 Now we\u2019ve added them to the work item form so you can still have a simple forward and backward experience even with a full screen work item.<\/p>\n

\"Image<\/a><\/p>\n

Links & Attachments tabs show count of contents<\/strong> \u2013 Now you don\u2019t have to go to the page to see if there is anything there.\u00a0 The tab itself will show you whether or not there\u2019s anything to look at.\u00a0 A nice little click saver.\u00a0 Notice that Storyboards, Implementation, All Links and Attachments all have counts next to them.\u00a0 Test Cases would too if I had created one.<\/p>\n

\"Image<\/a><\/p>\n

Generate a query for your backlog<\/strong> \u2013 A common request, since we introduced the new backlog tools, has been \u2013 how can I get my backlog in some other form \u2013 Excel, Project, VS query, etc.\u00a0 The problem is that the query that generates the backlog is not exposed.\u00a0 But not any longer.\u00a0 You can now generate a query that will match your backlog (both for the product backlog and sprint backlogs).\u00a0 You can then save that query in any query folder and then use it any way you can already use a TFS query \u2013 like opening it in Excel, etc.<\/p>\n

\"Image<\/a><\/p>\n

Visually remove items from backlog<\/strong> \u2013 Another bit of feedback we\u2019ve gotten is that the backlog is confusing when you edit a work item from the backlog and change its state to \u201cRemoved\u201d.\u00a0 That\u2019s supposed to delete it from the backlog \u2013 because you\u2019ve \u201ccut\u201d the feature but it still shows up until you hit refresh.\u00a0 Not any longer.\u00a0 We\u2019ve changed it so that when you change a work item (change the state, the iteration, etc) in some way that causes it to no longer match the backlog criteria, it will automatically be removed from the view \u2013 you won\u2019t have to hit refresh.\u00a0 Maybe we\u2019re being a bit too anxious about this but we\u2019re a bit worried that people will get freaked out by things disappearing from their backlog so we\u2019ve added an info bar that tells you when we\u2019ve removed something and gives you a link to get details on why we removed it.<\/p>\n

\"Image<\/a><\/p>\n

\"Image<\/a><\/p>\n

Animation on the task board<\/strong> \u2013 Another piece of feedback we\u2019ve gotten is that when you\u2019ve got a lot of tasks on the task board and you are moving them around, it can sometimes be hard to see where in the pile of cards the dragged task landed.\u00a0 To help with that, we\u2019ve added a little animation to glide the card into position.\u00a0 That way, it\u2019s easier for your eye to catch where it landed.\u00a0 It\u2019s a bit hard to show the animation with a screenshot and I don\u2019t want to mess with a video right now so you\u2019ll just have to wait to see it for yourself \"Image<\/a><\/p>\n

Add Azure xaml template to existing Team Projects<\/strong> \u2013 We\u2019ve had enough people struggle with the manual steps to get Azure Continuous deployment configured for pre-existing Projects.\u00a0 We\u2019ve decided to go ahead and add the new Continuous Deployment build xaml template to everyone\u2019s project.\u00a0 It should be pretty seamless for you but that file will show up in your build templates folder.<\/p>\n

We\u2019ve also done a bunch infrastructure and performance work but if everything keeps being fast and reliable, just consider it successful \"Image<\/a><\/p>\n

Of course, as always, not all of these will show up in your account instantaneously.\u00a0 It will take several hours to get through updating all the accounts.\u00a0 As I said, it\u2019s not an earth-shaking list of changes but it\u2019s a bunch of small, nice things \u2013 largely driven by customer feedback.\u00a0 As we get new post Spring work ramped up and as TFS 2012 work ramps down, I hope to see the sprint deployments get even more interesting.\u00a0 I hope you enjoy the improvements and, as always, we appreciate any feedback you have.<\/p>\n

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

Well, the last 3 weeks were busy.\u00a0 We announced our Azure Continuous Deployment support and removed the invitation codes to open the service up to everyone.\u00a0 As I wrote in my Spring wrap up post, we\u2019ve kind of emptied the pipeline of all of the big stuff we\u2019ve had in progress.\u00a0 So this sprint, we\u2019ve […]<\/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":[11,5],"class_list":["post-3131","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-announcement","tag-tfs"],"acf":[],"blog_post_summary":"

Well, the last 3 weeks were busy.\u00a0 We announced our Azure Continuous Deployment support and removed the invitation codes to open the service up to everyone.\u00a0 As I wrote in my Spring wrap up post, we\u2019ve kind of emptied the pipeline of all of the big stuff we\u2019ve had in progress.\u00a0 So this sprint, we\u2019ve […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/3131","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=3131"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/3131\/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=3131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=3131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=3131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}