p4 job
Synopsis
Create or edit a defect, enhancement request, or other job specification.
Syntax
p4 [g-opts
] job [-f]
[jobName
]
p4 [g-opts
] job -d
jobName
p4 [g-opts
] job -o
[jobName
]
p4 [g-opts
] job -i
[-f]
Description
A job is a written-language description of work that needs to be performed on files in the depot. It might be a description of a bug (for instance, "the scroll mechanism is not working correctly") or an enhancement request (for instance, "please add a flag that forces a certain operation to occur") or anything else requiring a change to some files under Perforce control.
Jobs are similar to changelist descriptions in that they both describe changes to the system as arbitrary text, but whereas changelist descriptions describe completed work, jobs tell developers what work needs to be done.
Jobs are created and edited in forms displayed by p4 job
. The
user enters the textual description of the job into the form, along with
information such as the severity of the bug, the developer to whom the
bug is assigned, and so on. Because the Perforce superuser can change
the fields in the job form with p4 jobspec
, the
fields that make up a job may vary from one Perforce installation to
another.
When p4 job
is called with no arguments, a new job named
job
is created,
where NNNNNN
NNNNNN
is a sequential six-digit number. You can change the job’s
name within the form before quitting the editor. If p4 job
is
called with a jobname
argument, a job of that name is created; if that
job already exists, it is edited.
Once a job has been created, you can link the job to the changelist(s)
that fix the job with p4 fix
, p4
change
, or p4 submit
. When a job is linked to a
changelist, under most circumstances the job’s status is set to
closed
. (See Usage Notes for more information).
Form Fields
These are the fields as found in the default job form. Because the fields that describe a job can be changed by the Perforce superuser, the form you see at your site may vary.
Field Name | Type | Description |
---|---|---|
|
Writable |
The job’s name. For a new job, this is Alternately, you can name the job anything at all by replacing the text in this field. |
|
Writable Value |
The value of this field must be |
|
Writable |
The name of the user who created the job. |
|
Writable |
The date the job was modified. |
|
Writable |
An arbitrary text description of the job. |
Options
|
Delete job |
|
Force option. Allows Perforce administrators to edit read-only fields. |
|
Read the job form from standard input without invoking an editor. |
|
Write the job form to standard output without invoking an editor. |
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
N/A |
N/A |
|
- If the Perforce superuser has eliminated field ID#
102
(theStatus:
field) withp4 jobspec
, Perforce is unable to close jobs when the changelists to which they are linked are submitted. See thep4 jobspec
command and the Helix Versioning Engine Administrator Guide: Fundamentals for more information. - After a job has been created or changed, Perforce indexes the job so
that
p4 jobs
-e can locate the job quickly. The index keys areword
,fieldname
whereword
is a case-insensitive alphanumeric word. Values in date fields are stored as the number of seconds since January 1, 1970, 00:00:00.
Examples
|
Create a new job; by default, its name is of the form
|
|
Edit job |