SourceGear Support

Is the ability to create a cross project query in the windows client present in version 2.0 of Fortress?

It seems that the delete Fortress Item functionality is not on 2.0. This feature which exists in the web client is not in the windows client adter the upgrade. Is it ever going to be included?

The missing icons in the solution tree view of Visual Studio 2010 are now a critical issue for us. We rely on that visual cue to find if we are dealing with renegade files or simply as the fastest way to determine if we are online or offline. Without those icons I already had my developers spend une...

I take it then that there isn't such a feature in 2.0 either? If so then please count my vote in for that badly needed feature.

Currently using Foretress 1.1. What is the best way to delete items from (old items in DIsregard status) from Fortress? Thick client does not have delete feature. Thin client has a delete feature that once the delete is confirmed ignores the query that was made before and takes you each and every ti...

Beth,

I have sent you by email the required items. Could you please confirm you have received them?

I have no way here to upload images that I know of, so I can't post it.

Telmo

When using at-a-glance and drilling down on each individual section (i.e. Open Items, Unassigned, etc.) they all drill down to the correct filter of items. However, not estimated shows all items in that milestone. Any assistance would be greatly appreciated as this is a great feature as I am unable ...

Dear Linda, We have just recently encountered a similar issue. Scenario is as follows: 1. In Visual Studio 2008 using Enhanced Fortress/Vault Client 2. I check out file "test.aspx" in folder "main". 3. I go to folder "secondary" and "Get Latest" on that folder...

It would be great to know how the issue has been resolved for these forums to be of value to others. I have the same issue (unable to add an item due to a foreign key issue).

I have just recently upgraded from Vault to Fortress (FortressServer64_1_1_4_18402) 64bit on Windows 2008, SQL Server 2008. The upgrade was not smooth due to the registry issue (Wow6432Node was in fact an empty node). Also, supplying a local user name (i.e. VaultUser) which exists on the machine, no...