Customizing Check-in Actions in your Process Template
In my last post, I told users about a client side hack that we added to change the default check-in action from “Resolve” to “Associate”. Most of the time I’ve heard questions about this, it is because a team has customized their process template to no longer include the Resolve state or adopted a template that doesn’t have the concept of Resolve – our own SCRUM template comes to mind…
Last week, Aaron Bjork posted a much better solution for teams with custom process templates. Check it out if you need a solution for changing work item state when checking in changes but aren’t using the Resolve state.