AW: [p4] Question on Jobs and changelists

Graf, Christian GrafC at
Thu Dec 13 00:05:35 PST 2001


1.) Jobs is a very helpful instrument as interface to bugtracking or
creating release-notes.

2.) A job must not be closed by submit -  this is just the default setting: 
	Working with p4win e.g. you may set the status in the
changelist-dialogue before submit. (Though closed is default.)

3.)  JobStatus field on 'p4 change', 'p4 submit'
     'p4 change' and 'p4 submit' forms have a 'JobStatus' field not
     normally displayed.  This field sets the fix status for all jobs,
     rather than using the default 'closed'.  The fix status can be
     set per-job with undoc 'p4 change -s' and 'p4 submit -s' (q.v.).

	You'll find this & some more information on typing 'p4 help undoc'.
	See also: p4 admin doc & p4guide. Both you will find at p4's

4.) You may reopen a job - which you cannot do with a changelist.

5.) You may customize jobfields. (see the p4 docs for further information)

6.) You may use job-triggers looking for information in the jobfields and
decide depending on the result wether a submit is valid or not or what to do
with the state of a reported bug in your defect-tracking system. 

Best regards

Christian Graf 

business solutions AG
Vincenz-Prießnitz-Straße 3
76131 Karlsruhe, Germany
Tel.: +49 (0) 0 721. 66 34-0
Tel.: +49 (0) 0 721. 66 34-200
mailto:GrafC at

Vorstandssprecher: Hubert Becker, Prof. Dr. Joachim Hertel - Vorstand:
Andreas Reinicke, Ludwig Augustin
Aufsichtsratsvorsitzender: Werner Huttner
Sitz der Gesellschaft: Friedrichsthal/Saar. Handelsregister: Amtsgericht
Saarbrücken. HRB 11470

-----Ursprüngliche Nachricht-----
Von: Jeff Cyr [mailto:JeffC at]
Gesendet: Mittwoch, 12. Dezember 2001 19:59
An: perforce-user at
Betreff: [p4] Question on Jobs and changelists

As a new user I'm trying to get a handle on Jobs and their usefulness.
>From what I've read a job is a description of a change that needs to be
made (or an enhancement, etc.). Changelists can be linked to a job to
show what was changed to close out the job. What I don't understand is
the fact that if any single changelist linked to a job is submitted the
job status changes to closed. This confuses me because if I have 5
changelists linked to a job, then all 5 should be submitted in order for
the job to be closed, yet if I close any one of them the job gets
closed. If I should use only one changelist per job then what use is the
job when I can put the job description in the changelist description?

I'm sure this is simply a lack of perspective on my part, can anybody
out there explain it to me?

Jeff Cyr
ACE Computer Engineering, Inc.
321-728-7975 x107

perforce-user mailing list  -  perforce-user at

More information about the perforce-user mailing list