How to not automatically mark a task complete on check-in

[dist0rti0n]

When you associate a change set to a work item Fortress automatically wants to mark it completed. It would be nice to change this behavior so that you can choose what the default is - either checked or not.

Otherwise, its implied that you're creating a task for every single check-in you're performing. It's also frustrating if you forget to un-check the box because your ticket appears to suddenly be "lost" since it's not in an open state.

Would it be possible to get this changed and is there a work-around for the time being (a config value that can be manually modified somewhere, etc.)?

[lbauer]

There's no way to configure this in the current version. We do have feature request 10950 logged for it, and I've added your vote. I'm not sure when we might fix this, though.

[AjarnMark]

dist0rti0n, I'm guessing that you are on a 1.x version of Fortress because I remember the same frustrations of having to go flip the status back to Open in order to do additional check-ins if I had previously checked-in a partial remedy and left the box checked.

However, in version 2.x of Fortress, while the checkbox is still checked by default, the browse functionality is greatly enhanced so you can find, and check-in code against, an item that is not Open. For example, but using the Recent query option, or the At-A-Glance query, you can locate items that were marked complete by a previous check-in, but are not yet closed.

[dist0rti0n]

Thanks for the reply - I hadn't revisited the browsing since upgrading.

Still it would be nice if it remembered the last view so that I didn't have to go digging so much along with allowing me to toggle the default setting of the checkbox.

[obrion]

Is there any way to find out when feature requests are expected to be implemented? I am also interested in the ability to default the state of this checkbox to unchecked.

Robert O'Brion

[lbauer]

We don't always know ourselves until we start working on a new release and prioritize the many items we need to work on. Feel free to ask, and if we know, we'll let you know.