ТЕМА: Minnesota : devops sec - Kabrinskiy Eduard

Minnesota : devops sec - Kabrinskiy Eduard 2 років 10 місяців тому #30226

Кабринский Эдуард - Tfs task - Кабринский Эдуард


<h1>Tfs task</h1>
<p>[youtube]</p>
Tfs task <a href="remmont.com">News new</a> Tfs task
<h1>How to customize TFS 2010 work items and workflows</h1>
<p>There are a lot of project templates available for Team Foundation Server, but you often need to tweak them to suit your team. This post explains how to customize work item types and workflows.</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_62.png" /></p>
<h2>Team Foundation Server 2010 and add-ons</h2>
<p>We use Team Foundation Server (TFS) 2010 to manage our projects including source control, product backlogs, tasks, and bug tracking.</p>
<p>Our setup consists of:</p>
<h2>Customize a TFS work item</h2>
<p>When you install <strong>TFS Power Tools</strong> you get an additional menu option called <strong>Process Editor</strong> under <strong>Tools</strong> in Visual Studio 2010:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_16.png" /></p>
<p>The <strong>Process Editor</strong> allows you to edit work item types, either globally or for a specific TFS project.</p>
<p>For example, we can modify the <strong>Task</strong> work item type to add a custom field by clicking <strong>Work Item Types</strong> and selecting <strong>Open WIT from Server</strong>:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_23.png" /></p>
<p>This brings up a dialog with the available TFS projects. So, if we want to modify the <strong>Task</strong> work item type for our website’s TFS project we’ll simply expand its node and select the <strong>Task</strong> work item type:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_42.png" /></p>
<p>We click <strong>New</strong> on the <strong>Fields</strong> tab to add a custom field:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_52.png" /></p>
<p>Next, we give our new field a name, a reference name, and optionally a description:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_62.png" /></p>
<p>Next, let’s add a <strong>rule</strong> for specifying available value options for this field. We click the <strong>Rules</strong> tab and click the <strong>Add</strong> button:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_72.png" /></p>
<p>We’ll select the <strong>SUGGESTEDVALUES</strong> option in the next dialog…</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...d-image_thumb_92.png" /></p>
<p>…and then we set <strong>group restrictions</strong> (optional) and click the <strong>New</strong> button to add our options:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_122.png" /></p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_102.png" /></p>
<p>When we’re done we can switch to the <strong>Layout</strong> tab to add our field to the work item editor:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_132.png" /></p>
<p>We’ll set a <strong>label</strong> for the control and select the <strong>field</strong> we created earlier:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_142.png" /></p>
<p>Now, if we create a new <strong>Task</strong> work item…</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_152.png" /></p>
<p>…we’ll be able to see our new custom field in action:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_172.png" /></p>
<h2>Modify a TFS work item workflow</h2>
<p>To modify a <strong>workflow</strong> you open up the <strong>work item</strong> associated with the workflow. We could for example modify the workflow for the <strong>Bug</strong> work item type in order to add additional <strong>states</strong> to make it fit our work process:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_182.png" /></p>
<p>We click the <strong>Workflow</strong> tab to edit the workflow associated with the <strong>Bug</strong> work item type:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_192.png" /></p>
<p>The original workflow for the <strong>Bug</strong> item type in the Visual Studio Scrum 1.0 template takes bugs from <strong>New</strong> to <strong>Approved</strong> to <strong>Committed</strong> and finally to <strong>Done</strong> – unless they are <strong>Removed</strong>:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_202.png" /></p>
<p>We want to <strong>rename</strong> some of these different states, and also <strong>add a few new ones</strong>. We do this by pulling up the standard Visual Studio toolbox which, when a workflow is being displayed, gives a few basic – but useful – artifacts to customize the workflow:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_212.png" /></p>
<h3>Renaming a workflow state</h3>
<p>First off we want to rename the somewhat confusing “<strong>Approved”</strong> state to “<strong>Verified”</strong> (indicating that the reported bug <em>is indeed</em> a bug), so we simply double-click the red state object and change its name to “Verified”:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_222.png" /></p>
<p>We also change the name of the “<strong>Committed</strong>” state to “<strong>In progress</strong>”:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_242.png" /></p>
<p>When the bug is <strong>done</strong> we consider it to be in need of approval, so we change the name of the “<strong>Done</strong>” state to “<strong>Awaiting approval</strong>”:</p>
<p>In order to allow a product manager, or other similar role, to approve the resolution of a bug we need to add two additional states: “<strong>Accepted</strong>” and the less popular “<strong>Not accepted</strong>”. We do this by adding a new <strong>State</strong> object to the workflow:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_272.png" /></p>
<p>We double-click the new <strong>State</strong> object and name it “<strong>Accepted</strong>”. We repeat this process for the “<strong>Not accepted</strong>” state:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_282.png" /></p>
<p>To connect the workflow states we click the <strong>Transition Link</strong> tool in the toolbox and then we click the “<strong>Awaiting approval</strong>” state followed by the “<strong>Accepted</strong>” state. We repeat this for the “<strong>Not accepted</strong>” state:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_302.png" /></p>
<p>When two <strong>state</strong> objects have been connected by a <strong>transition link</strong> we see a new blue <strong>transition</strong> object. We can click the downwards-pointing double arrow to modify the <strong>transition</strong> object:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_312.png" /></p>
<p>Each transition must be given a <strong>reason</strong> which explains why the workflow progressed from one <strong>state</strong> to the next.</p>
<p>To set the <strong>reason</strong> why the workflow goes from “<strong>Awaiting approval</strong>” to “<strong>Accepted</strong>” we double-click the <strong>transition</strong> object connecting them. This brings up the <strong>Workflow Transition</strong> dialog:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_322.png" /></p>
<p>We switch to the <strong>Reasons</strong> tab to set the reason(s) the change in <strong>state</strong> can occur. Simply click <strong>New</strong> to add a new reason:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_332.png" /></p>
<p>In this case we’ll say that there are two reasons a <strong>Bug</strong> item can go into the “<strong>Accepted</strong>” state: 1) the customer has accepted the resolution (this is the default), or 2) the bug was accepted and given the OK by a developer.</p>
<p>First we’ll add the <strong>default reason</strong>, when the customer has accepted the fix:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_342.png" /></p>
<p>Note that <strong>field rules</strong> can be applied on the <strong>Fields</strong> tab if necessary.</p>
<p>We’ll also add the second <strong>reason</strong> a <strong>Bug</strong> can become “<strong>Accepted</strong>”, when a developer gives it the OK:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_352.png" /></p>
<p>So, we now have two <strong>reasons</strong> for a <strong>Bug</strong> going into the “<strong>Accepted</strong>” state:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_362.png" /></p>
<p>We’ll repeat this process for the <strong>transition</strong> from “<strong>Awaiting approval</strong>” to “<strong>Not accepted</strong>”.</p>
<p>We will also add <strong>another transition link</strong> to allow the <strong>Bug</strong> item to go from “<strong>Not accepted</strong>” to “<strong>In progress</strong>” to allow us to have another go at fixing the bug.</p>
<p>All in all, our revised workflow looks like this:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_372.png" /></p>
<p>Once a <strong>Bug</strong> is “<strong>In progress</strong>” it can be set as “<strong>Awaiting approval</strong>” (because we believe it has been fixed). The customer can agree which would make the bug resolution “<strong>Accepted</strong>”. If the customer does <em>not</em> agree, the <strong>Bug</strong> will go into a state of “<strong>Not accepted</strong>” which in turn means we can start working on it again by setting the state to “<strong>In progress</strong>”.</p>
<p>We can now try and modify the <strong>State</strong> field for a <strong>Bug</strong> item to see the workflow in action. For example, we see that from the “<strong>Awaiting approval</strong>” state we can go to the “<strong>Accepted</strong>” or “<strong>Not accepted</strong>” states:</p>
<p style="clear: both"><img src="tedgustaf.com/contentassets/fd386250a4f1...-image_thumb_392.png" /></p>
<p><strong>Note:</strong> The workflow could optionally be complemented with a <strong>transition link</strong> from “<strong>Accepted</strong>” to “<strong>Not accepted</strong>” with a reason saying the bug was <strong>re-opened</strong>.</p>
<h2>Tfs task</h2>

<h3>Tfs task</h3>
<p>[youtube]</p>
Tfs task <a href="remmont.com">Top news today</a> Tfs task
<h4>Tfs task</h4>
There are a lot of project templates available for Team Foundation Server, but you often need to tweak them to suit your team. This post explains how to...
<h5>Tfs task</h5>
Tfs task <a href="remmont.com">Tfs task</a> Tfs task
SOURCE: <h6>Tfs task</h6> <a href="dev-ops.engineer/">Tfs task</a> Tfs task
#tags#[replace: -,-Tfs task] Tfs task#tags#

Kabrinskiy Eduard
top news
  • SHEQELBoolo
  • SHEQELBoolo аватар
  • Немає на сайті
  • Платиновий учасник
  • Дописи: 3182
  • Репутація: 0
Адміністратор заборонив доступ на запис.
Час відкриття сторінки: 0.056 секунд