![]() ![]() A lot of things about Microsoft gives me that impression and, for me, it is hard to swallow. It seems to me Microsoft is being heavy-handed forcing development teams to do it the way they think it should be done versus giving the teams the flexibility to find what works for them. With this new job I am getting back into the Microsoft stack (I left it for ~5-6 years for the JBOSS/Tomcat/Apache/Linux stack). What is frustrating to me is it seems that it would be better to allow the scrum team to define their scrum board to map to their process separate from what the product owner is doing on the BPI/Story board. This is great for the PO to track their process in preparing work for the team. I don’t mind and kind of like the separation of concerns around the fact that epics, features, BPI/Stories have their own boards. It seems that during a sprint team members have to view both the BPI/UserStory board and the sprint board to get the full picture of what is happing with a BPI/Story in context of the sprint. In TFS 2015 the scrum board is fixed based on the BPI (or User Story depending on the Process Template you are using). It gave the QA member information around when a story was ready for testing, it gave DevOps information about when an item could be deployed, etc. Issue: Using JIRA there was one scrum board per team and that all roles on the scrum team use the scrum board to understand where stories are in the process during the sprint. I changed companies and they are using TFS 2015. "AssociateAsDefaultCheckinAction.reg"Įxecute the reg file on the developers systemĪfter that, restart visual studio and check the result.Background: I have worked with many scrum teams over the past 5 years using Atlassian JIRA. But in case you are not familiar with RegEdit and you are searching for an automated way for the roll out, use the reg file instead.Ĭreate a registry file with name e.g. Replace 12.0 (for VS2013) with 14.0 for VS2015, 11.0 for VS 2012 or 10.0 for VS 2010.īased on the answer of DaveShaw and in respect to VS2022, my answer does not contain new information. HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\TeamFoundation\SourceControl\Behavior\ResolveAsDefaultCheckinAction to False. Drag tasks to a downstream column to reflect if they are in progress or completed. To make “Associate” the default action (instead of “Resolve”), set the registry key The Taskboard makes quick work of updating both task status and remaining work. There is also another way to do this that only affects your client machine: There are probably more ways to do this, it all depends on the team and environment you work in :). ![]() The Professional Team Foundation Server 2010 book from Wrox will help with WIT editing. You can then transition you work items to this state whist working on them and then back to "Assigned" (or whatever) before checking them in in and "Resolving" them. "Under Development") that doesn't have an ACTION of Checkin. The other option is to add a new work item "State" (e.g. Section from your template - it will be in the against a particular transition between 2 states.ĭoing this means TFS will never transition your work item as part of your checkin, you will have to do it every time. Open the XML for your Work Item Type (or the GUI in the Power Toys if you prefer): One option is to remove the "Resolve" option altogether, you can do this as follows: You will need to edit the Work Item Template definition for the types of work items you are using (Bug, Task, etc.). To make this the Default is more complicated. ![]() When you are in the Pending Changes panel ready to check in your fix and you associate you work item with the changeset you should change "Resolve" to "Associate" (or what ever it is in Scrum). We are using Scrum 2.0 template from Microsoft. So my questions are: How to disable this? Is this feature part of template or some much more deeper integration with TFS work item management? Automatic done movement is pretty annoying automation which shouldn't be there. With taskboard feature in scrum template moving tasks to done after work is done is anyway trivial and common part of workflow. Yes this is doable but it isn't as nice workflow as it may be. The only way to do this (which I know) is to select the task for my current work just before I merge all small commits from my personal branch to master. How can I disable this? I'd like to have the development branch so that I can make small commits during development but with this feature I cannot connect the task with my current work if I do so. After you have connected the task with your work item, any checkin to any branch will mark the task to "done" status. However, there is a very annoying feature with "My Work" feature if you connect your work with a certain task. We just moved to use TFS 2012 which seems to be a huge upgrade for 2008 in usability with VS2012. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |