Add a New Assignment
This section provides information about adding a new assignment.
A – Create Assignment
Type A or ADD on the Container List Command line and press Enter to create a new Container. The Add/Create New Container screen is displayed, as shown in the following figure.
Create Assignment
COMMAND ===>
Container Type A (A-Assignment, R-Release)
Description __________________________________________________
Assignment Prefix PLAY (Assignment Prefix )
Assignment Owner USER003 (Defaults to user creating container)
Assignment Tag ____ (Optional, free form tag for user)
Default Application PLAY____
Default SubAppl PLAY____ (Sub Application)
Default Stream PLAY____ (PLAY)
Default Path DEV1 (DEV1 DEV2 FIX)
Default Release __________ (Optional, default Release for Tasks)
WORK REQ ________________________ (Optional)
Join Users N (Y-Join Users to Assignment)
Sandbox Codeline _ (Y-Create Sandbox Codeline)
Join At Level ____ (Optional, specify Join At Level for Sandbox)
Press ENTER to Add/Create new Assignment, END to terminate
Adding/Creating new Assignments and Releases
On the input screen shown in the preceding figure, the Container Type defaults to A for Assignment, but may be overtyped to R for Release. The input fields on the screen then change accordingly. See Add-a-New-Release for further details on releases.
Application and SubApplication and Stream
Most of the modules within the Assignment are expected to belong to this Application and SubApplication and Stream. These values will be the defaults displayed on the Task Add screen when adding tasks to this Assignment. Modules from other Application and SubApplication and Streams can be added to this Assignment, if required, by overtyping the defaults on the Task Add screen.
The Application and SubApplication and Stream values on the Add New Container screen default to the last values entered on this screen, but may be overtyped to different values.
Assignment names
An assignment name is a 10-character Container Name that is system-generated. User-specified names cannot be used. Code Pipeline uses an Assignment Prefix and generates a sequentially incrementing number for the suffix.
The Code Pipeline Administrator will have defined one or more Assignment Prefixes in Code Pipeline, which can be between 1 and 4 characters long. Sometimes the Prefix will be the same as an Application code.
Specify the appropriate Prefix in the Assignment Prefix field, and Code Pipeline will generate an Assignment name. For example, an Assignment Prefix of PLAY will result in the names of PLAY000001, PLAY000002, and so on.
Other input fields
The following table describes the other input fields:
Fields | Description |
|---|---|
Assignment Tag | (Optional) 4-character free form field. |
Container Owner | Defaults to the UserID of the person creating the Assignment, but may be overtyped to another valid UserID. |
Description | Text field. |
Default Path | The default starting/update level for Tasks in this particular Assignment, which depends on the Application and Stream values specified. (If the Application and Stream values have been typed in but the Default Path is still blank, pressing Enter will show the valid Start Levels to choose from.) |
Default Release | (Optional) Used to associate logically related Assignments. Tasks added to the Assignment will default to this Release. |
WorkRef | (Optional) Site-definable field typically used to associate the Assignment with a problem ticket number or change request number. |
Join Users | Defaults to No. Use Y to immediately join other users to the new Assignment. |
Task Add Screen is displayed
Once the Assignment has been added, the Task Add screen is displayed so that modules or Tasks can be added immediately. PF3 back if adding modules or Tasks is not currently required.
For more information on Adding Tasks, see A – Add Task.