Received: from [172.16.1.179] (root@raven.ravenbrook.com [193.82.131.18]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id AAA26865 for ; Tue, 31 Oct 2000 00:31:43 GMT Mime-Version: 1.0 X-Sender: gdr@pop3 (Unverified) Message-Id: Date: Mon, 30 Oct 2000 16:30:23 -0800 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Mahi Networks alpha test notes, 2000-10-30 Content-Type: text/plain; charset="us-ascii" ; format="flowed" This is a report on defects discovered during alpha testing at Mahi Networks. 1. Do a "complete install" of TeamTrack to overwrite the previous version, rather than an upgrade. (Why, exactly?) 2. Could we use Python to update the registry? 3. Use e-mail addresses to map between user IDs on each system? 4. P4DTI user has to be a super user in Perforce. This isn't documented. Does it really need to be super? Probably to edit the jobspec, but maybe not later. 5. Can we automatically set up a jobspec from the TeamTrack field definitions 6. Can't have a single-select field with values which has slashes in it. Mahi's version name has both slashes and spaces. 7. You don't say "required" in Perforce for a required field in TeamTrack, because in TeamTrack it might be required only on some transitions. Instead, make it default to something illegal in TeamTrack so that the Perforce user has to fill it in to make the transition, for example, "$blank". 8. Some people use IIS to server TeamTrack, so we shouldn't advise them to restart the TeamTrack web server. 9. Typo "replucator" in SAG. 10. Single select fields in TeamTrack can also have the value zero with name '(None)', meaning that the field doesn't have a value yet. The code for replicating such a field back from Perforce needs to take account of this. Note that this has bitten us several times: check every field and every transition we do and see if it could be (None) and if so whether we do the right thing. 11. It looks to me as though replication of pending changes isn't doing the right thing. 12. We need to think about how to make workflow maintenance easier, so that changes only need to be made in one place, in TeamTrack, and not done in the configuration and also the jobspec. 13. It would be nice if fixes showed in the revision history or filelog in Perforce. 14. Change comments and the fixes table may be the most important thing to see in TeamTrack. Need to give a lot of prominence to the change comments. 15. Mahi would like to be able to build a single field like Fix Description by (say) concatenating all the change descriptions. 16. We've seen several times that we attempt an illegal transition. The transition goes through; then TeamTrack fails and apparently refuses to transition it; but the event log was full so we couldn't find out why. 17. The replicator does an overwrite by (1) doing the transition and (2) setting the action field. This appears as two entries in the state change section of the issue description in TeamTrack.