locked
Custom fields in user story and other work items RRS feed

  • Question

  • Hello!

    Maybe somebody has asked this question on this forum before, but we have TFS Version 15.105.25910.0. And we are planning to add custom fields to our work items, because we want to track for example which user stories and bugs have been installed into production and when. We are using Agile project template and unfortunately there is no field(s) on work items that could describe this kind of need. We could use tags (installed 2017-04-01) and then make queries against it, but we don't want to add a new tag everytime for a work item(s) when we install new version of our products, because soon there will be large number of useless tags and queries. We want to keep our tags clean and reusable.

    To overcome aforementioned problem we would like to add custom fields that we could add information when each user story has been installed. Is there any other way to do this? If not, we would like to know if we will upgrade our TFS to newer version, will the custom fields and their's stored data disappear after upgrading?

    What is the best solution for this kind of problem?

    Thursday, April 27, 2017 12:02 PM

All replies

  • Hi Reinipa,

    Create a new work item field to track the information which you need is a good method.

    The custom fields and their stored data is stored in the database, it will not disappear after upgrading.

    You could create custom field without concern.

    Best Regards


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, April 28, 2017 3:24 AM
  • Thanks, this helped us a lot!
    Tuesday, May 2, 2017 7:40 AM
  • Hi Reinipa,

    If my reply is helpful, could you please mark it as answer?

    So it would be helpful for other members who meet the same issue as yours.

    Best Regards


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 3, 2017 8:21 AM