[p4] customization of changeset number

[David Weintraub]

Instead of using the Changelist number, look at Perforce's Job ID
system. Perforce's Job ID can match TeamTrack's issue ID, and then
when you submit a changelist, you can attach multiple job IDs on the
changelist. Perforce jobs have a status/state field which can point to
whether the Perforce job is assigned to a developer, being worked on
by a developer, or has been closed by a developer. This is a much
better way to integrate Perforce with TeamTrack.

In fact, there's already a package called P4TDI which you can get from
Serena for free. Perforce will even give you an extra user license to
use with P4TDI.

P4TDI uses a Python script to watch both the jobs in Perforce and the
Issues in TeamTrack, and synchronizes them every few seconds. Any
change in an Issue in TeamTrack will be reflected in Perforce, and any
change in the Perforce Job will be reflected in the TeamTrack Issue.

On 4/3/07, Kilaru Sambaiah <ksambaiah at gmail.com> wrote:
> Hi All,
>   I am new to perforce and it is my first post. I am wondering, whether it
> is possible to customize the changeset
>   number?
>
>   We are using teamtrack for long time and teamtrack id is something like
> 000024689, we are planning to migrate
>   SCM to perforce.
>   My question is upon submit, perforce gives changeset number like 15 or 16,
> but my teamtrack id is what I wanted
>   to be changeset number. Is it possible to customize?
>
> thanks and regards,
> Sam
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
--
David Weintraub
qazwart at gmail.com