![]() I rank this option in my “OK” category because at least VSOnline teams can now configure this behavior regardless of the process template chosen at team project creation time. OK for TFS Cloud/ Visual Studio Online users. (See half-way down my last blog article for the ranking system I’m using.) My ranking and rationale for this feature: (This option is the out-of-box option for team project’s configured to use the MSF-Agile process template.) (This option is new.)ģ. Have bugs managed separately through work item queries rather than clutter their backlog or task board with that detail. (This option has been the out-of-box behavior for those team projects configured using the Scrum or CMMI process template.)Ģ.Have bugs appear on the task board alongside of the task-level work items which are tracked as a part of what needs to be done for a requirement to be called “Done.” These will also appear in the team’s backlog as child work items under the requirement to which they are attached. ![]() Have bugs appear on the team’s backlog and assigned to iterations along with their process template’s requirement-level work items. One of the ballyhooed features of Team Foundation Server 2015 is that individual teams in a team project (regardless of the process template their team project was configured to use and without customizing the process template) can now configure for themselves how/where they want to manage bug work items in one of 3 ways:ġ. ( Note: This post makes heavy use of links to official documentation to allow users new to TFS to investigate the concept via official documentation and yet keep this article on-point of communicating information not readily apparent by reading that documentation).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |