1 message in com.perforce.perforce-userRe [p4] P4DTI with TeamTrack
FromSent OnAttachments
Ilya Rokhkin21 Feb 2004 23:36.py
Subject:Re [p4] P4DTI with TeamTrack
From:Ilya Rokhkin (il@direct-solution.com)
Date:02/21/2004 11:36:44 PM
List:com.perforce.perforce-user
Attachments:

Hello Andrew

It seems to me that you didn't defined TeamTrack "Close_State" in you config.py
file closed_state = "Resolved" State Resolved goes right after Assign state. It is like in Sample Database in TeamTrack 5.8 It depends on your WorkFlow "closed_state" should be something that goes
directly after Development state (Assigned) and have Transition to state
"Resolved" from "Assigned" Attached Config_orig.py file where there is right settings for Sample project of
TeamTrack 5.8

With best regards. Ilya Rokhkin ilya at direct-solution.com Application Engineer. Direct Solution Ltd., Israel Tel: (972)-9-7466661 Fax: (972)-9-7466477

Hello,

Has anybody out there got a perforce to TeamTrack integration using the P4DTI to
work?

I am working at a job where I have inherited someone else???s implementation and
right now I am getting errors emailed from the P4DTI to me every time some one
submits a change list with a job fix. The error I get is

(P4DTI-6142) No transition from state 'assigned' to state 'closed'

and I have checked the workflow in TeamTrack and this is a valid transition.

Anyone have any experience with this?

Thanks, Andrew