P4 Operation Timeout settings changed from 1.6.x to 2.x

In fisheye 1.6.6 you could simply enter a number such as 10 for the P4 Operation Timeout.

Fisheye 2.1 forces you to specify the time units such as 10 minutes.

The problem is if you upgrade from 1.6.x you won't be able to edit the value through the web interface and an error is logged:

java.lang.IllegalArgumentException: commandTimeout '10' is not valid
        at com.atlassian.fisheye.spi.admin.data.P4RepositoryData.setCommandTimeout(P4RepositoryData.java:142)
        at com.atlassian.fisheye.spi.admin.impl.AdminSpiUtil.copyP4FieldsToRepData(AdminSpiUtil.java:257)

We should default the timeout to use minutes if no unit is specified.

The fix is to edit your FISHEYE_INST/config.xml and change the commandTimeout attribute to specify the time units on the <perforce> element

<perforce casesensitive="true" path="//depot/" initial-import="false" 
   port="1666" server="erdinger" skip-labels="false" 
   unicode="false" command-timeout="10 minutes">