The upgrade was done on a different server than the original Vault location.
I moved the database and installed Fortress and it upgraded the database.
The Vault portion of the upgrade seems to be OK.
I ran into/am having the following issues:
- I found the documentation on the Fortess Item Tracking portion of the system to be lacking as I tried to setup the fields.
I would have been a lot easier if there was something which would have given me some guidance on what fields are required to be setup on the Admin -> Item Track Fields interface.
After trying to examine some of the database tables, I think I determined at all of them are required.
I would also have liked a "white paper" on scenarios/best practices for using and setting up the item tracking system projects, etc. - When I go to the Add Item screen, there is no visual indication of which fields are required and which are optional.
I request that you add a visual indicator to the Add Item screen(s).
Bold the field title or place a red asterisk after the label or something.
The current screen is not very user-friendly. - I am unable to create any Fortress Items.
I am getting the following error
Error: 547, The action can not be performed. Other items in the database depend on the value you are modifying
with the following in the log file:Helpers::AddItem The INSERT statement conflicted with the FOREIGN KEY constraint "fk_items_itemstatuses".
The conflict occurred in database "sgdragnet", table "dbo.itemstatuses", column 'statusid'.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at MantisSQLService.MantisSQLService.AddItem(MantisSqlConn conn, Int32 nAuthUID, MantisItem& mItem, String strXmlKeywords, String strXmlTags, Int32 nAttDBBufSize)
at MantisServiceAPI.MantisServiceAPI.AddItem(Int32 nAuthUID, String strUserLogin, MantisItem& mItem, Int32 nAttDBBufSize)
at MantisServiceLib.Helpers.AddItem(HttpSessionState session, MantisItem& mItem) -
When using the FortessPlugIn for CruiseControl.NET finally got it working but in several attempts had to kill the build process after 3 hours
(which normally takes about 20 minutes).
Apparently the FortessPlugIn does not support a Timeout parameter.
It really needs to in the same manner the standard Vault tasks in CC.NET do.
Thank you.
Larry