To add a field in TFS Agile Template or live with Defaults?
<p><strong>What we know:</strong>
Tfs allows us to manage bugs. We can add bugs and move it through different states.</p>

<p><strong>What we need:</strong>
We need to have different states in bug, which TFS 2015 doesn't allow out of the box, particularly </p>

<ul>
<li>"<strong>Not a Bug</strong>" (which is after NEW > ACTIVE  and then if Developer says, its not a bug)</li>
<li>"<strong>RE-Opened</strong>" (where a bug has traversed from NEW > ACTIVE > RESOLVED > CLOSED and then Re-Opened in another Release / Sprint).</li>
</ul>

<p><strong>Which approach mentioned below we could use ?</strong> </p>

<p>A- We are currently on TFS 2015. We do the customization through WITAdmin approach (<a href="https://www.visualstudio.com/en-us/docs/work/customize/add-modify-field" rel="nofollow noreferrer">https://www.visualstudio.com/en-us/docs/work/customize/add-modify-field</a> )  and it's impact on Database, Reporting and going forward, towards migration would be another effort.</p>

<p>B- We migrate our TFS 2015 to TFS 2017 and get the new feature of adding our new states out of the box as per (<a href="https://www.visualstudio.com/en-us/docs/work/process/customize-process-field#add-a-custom-field" rel="nofollow noreferrer">https://www.visualstudio.com/en-us/docs/work/process/customize-process-field#add-a-custom-field</a>)</p>

<p>C- We need to change our practice of logging bugs, and we need to study proper Agile Implementation through TFS, since AGILE process does have this scenario of <strong>What We need</strong> mentioned above.</p>

<hr>

<p>A,B,C are the approaches, I have thought about. I would appreciate if the experts could share their experiences, thoughts and / or new approaches. </p>