{"id":863,"date":"2014-08-04T23:31:00","date_gmt":"2014-08-04T23:31:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/08\/04\/work-items-tracking-using-release-management\/"},"modified":"2022-05-26T07:57:40","modified_gmt":"2022-05-26T15:57:40","slug":"work-items-tracking-using-release-management","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/work-items-tracking-using-release-management\/","title":{"rendered":"Work-items tracking using Release Management"},"content":{"rendered":"<p>Tracing what is new in a given release for a product is often tiresome and time taking task. With Microsoft Release Management 2013 Update 3 RC\/RTM, you can achieve this easily through its \u201cChange Summary\u201d feature. Details of this feature is described below<\/p>\n<h2>Change Summary feature details<\/h2>\n<h3>Manual Release<\/h3>\n<p>When you start a new manual release from the Release Management client, it takes you to the Release page. Now, on this <strong>Release<\/strong> page, there is a new tab \u2013 <strong>Change Summary<\/strong>:<\/p>\n<p>\u00a0<img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/08\/5353.1.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>\u00a0<\/p>\n<p>Click on the <strong>Change Summary<\/strong> tab and it shows you the list of work-items that are new or changed in the current release (in progress). This list is a relative list of work-items that are new \/ changed \/ implemented in the current release <span style=\"text-decoration: underline\">w.r.t. last successful release<\/span> of the application:<\/p>\n<p>\u00a0<img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/08\/3660.2.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>You can also go to the already completed releases and you can see the <strong>Change Summary<\/strong> for each of these releases.\u00a0<\/p>\n<p>The <strong>Change Summary<\/strong> shows Id, Type, Title, Owner and State of the work-items. Should you want to look at the individual work-items in more detail, you can do that by clicking on the Id field&#8217;s link which leads you to the work-item on TFS.\u00a0<\/p>\n<p>\u00a0<\/p>\n<p><em>Note: Change summary shows the work-item differences per Stage. So if you are looking at change summary on a given stage, it compares work-items with last successful release <span style=\"text-decoration: underline\">on that stage<\/span> only and shows all the new \/ changed work-items since last release till the current release (in progress) <span style=\"text-decoration: underline\">for that stage<\/span>.<\/em><\/p>\n<ul>\n<li><\/li>\n<li><\/li>\n<\/ul>\n<h3>Automated release (Continuous deployment process)<\/h3>\n<p>Many a time releases are triggered not manually but as part of continuous deployment process setup or through command line utility. In such cases, a Release Manager or a project manager or a Stage owner would like to view the Change Summary of work-items before approving\/rejecting a release or any step in a release. For this, he\/she need not come to the Release Management client but can do so through the Release Explorer (web client).<\/p>\n<p>The Release explorer, now, contains an additional link for Change Summary which shows the list of new \/ changed work-items:<\/p>\n<p>\u00a0<img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/08\/1727.3.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>On clicking this you can see the work-items diff in the same way as on the Release Management client:<\/p>\n<p>\u00a0<img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/08\/6787.4.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>\u00a0<\/p>\n<h3>Feature limitations<\/h3>\n<ul>\n<li>\n<p>This feature is only available in the vNext deployment pipeline. To know more about vNext deployments, you can refer these articles:<\/p>\n<\/li>\n<li>\n<p><a title=\"Deploying using PowerShell Desired State Configuration in Release Management\" href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/07\/22\/deploying-using-powershell-desired-state-configuration-in-release-management.aspx\" target=\"_parent\" rel=\"noopener\">Deploying using PowerShell Desired State Configuration in Release Management<\/a><\/p>\n<\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/07\/07\/how-to-setup-environments-for-agent-less-deployments-in-release-management-release-management-2013-with-update-3-rc.aspx\" title=\"How to setup environments for Agent-less deployments in Release Management 2013 with Update 3 RC\">How to setup environments for Agent-less deployments in Release Management 2013 with Update 3 RC<\/a><\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/07\/07\/how-to-deploy-to-standard-or-azure-environments-in-release-management-2013-with-update-3-rc.aspx\" title=\"How to deploy to Standard or Azure environments in Release Management 2013 with Update 3 RC\">How to deploy to Standard or Azure environments in Release Management 2013 with Update 3 RC<\/a><\/li>\n<li>\n<p><a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/07\/08\/how-to-trigger-deployments-to-chef-managed-environment-from-release-management.aspx\" title=\"How to trigger deployments to Chef managed environments from Release Management 2013 with Update 3 RC\">How to trigger deployments to Chef managed environments from Release Management 2013 with Update 3 RC<\/a><\/p>\n<\/li>\n<li>\n<p>Currently the feature works when you use TFVC as source control. If you use Git, this feature would not be available.<\/p>\n<\/li>\n<li>This feature can provide work-items across multiple branches if the same is reflected through the Source directories listed on the build definition.<\/li>\n<li>Work-items from child branches with FI and RI into the working branch would not be available<\/li>\n<li>When you choose &#8220;Build Externally&#8221; with components, work-items are not available as this information is not available in the builds of these components.\n\u00a0<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Tracing what is new in a given release for a product is often tiresome and time taking task. With Microsoft Release Management 2013 Update 3 RC\/RTM, you can achieve this easily through its \u201cChange Summary\u201d feature. Details of this feature is described below Change Summary feature details Manual Release When you start a new manual [&hellip;]<\/p>\n","protected":false},"author":139,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[226,1],"tags":[],"class_list":["post-863","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ci","category-devops"],"acf":[],"blog_post_summary":"<p>Tracing what is new in a given release for a product is often tiresome and time taking task. With Microsoft Release Management 2013 Update 3 RC\/RTM, you can achieve this easily through its \u201cChange Summary\u201d feature. Details of this feature is described below Change Summary feature details Manual Release When you start a new manual [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/863","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/139"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=863"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/863\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}