Copying tasks from another change request
The Copy Change function enables you to copy a request into a new change request. When using the copy function, you have the option to copy the tasks associated with the original change request.
To copy tasks from another change request
- From the left navigation pane on the Change form, choose Functions > Copy Change.
- On the Copy Infrastructure Change dialog box, select Copy Tasks.
- On the Copy Tasks dialog box, you can select the tasks that you want to exclude from copying. You can select the tasks either by status (Cancelled, and Failed) or by type (Manual, and Automatic).
- Select the related task information that you want to copy, and then click OK.
Depending on the options that you select, the following information is copied to the new change request:
Option
Copied information
Location Information with Attachments
The following information from the General tab related to Task Location and the Task Attachments, except Command field:
- Company
- Region
- Site Group
- Site
- Address
- All related attachments
Requester Information
The following information from the Requester tab:
- Requester Company
- First Name
- Middle Name
- Last Name
- Phone Number
- Organization
- Department
- Support Organization
- Support Group Name
Work Info with Attachments
All information on the Work Info tab including any attachments
Relationships
All information from the Relationships tab
Dates
The following information from the Dates tab is copied:
- Schedule start date
- Schedule end date
Financials
The following information from the Financials tab:
- Calculation Unit type
- Budget Estimated Total Time
- (optional)Enter values in the following fields under Tasks Details to be overwritten in all copied Tasks:
- Specify a value in the Summary field.
If you specify a summary value, the Summary field of all the new copied tasks uses this value. Otherwise, the Summary field of all the new copied tasks uses the values of the source tasks. - Select the Priority of the task.
- You can enter notes in the Notes field.
- Specify a value in the Summary field.
Click Start Copy.
Note
It can take several minutes for the copy process to be completed.
All tasks and child tasks related to that task are copied. After the change is copied, the Change form opens in New mode with the newly copied change information in a Draft status. Any tasks that are copied are in Staged status. You now can modify and submit the new request.
Save the new copy of the request.
Note
A copied change request is not automatically submitted.
Comments
Is this functionality working as designed in CM 8.1?
When copy a closed change request with tasks the new change and its task is staged is status Pending Assignment. When the change is approved the tasked will not move on - they are stocked in Pending Assignment.
Repeating to be sure I got this right: When a change is copied along with task, the copied tasks are in "Staged" status.
Now, when the change moves to "Scheduled" status, and if there are assignees for the task (which could happen due to auto-assignment), the status of the "first" tasks (there can be more than one such task) is changed to "Assigned".
If there are no assignments for the first task, the status will be "Pending" status. The approval step moves the change to "Scheduled" status, which activates the tasks and changes their status. Even without approval configuration, when the change moves to "Scheduled" status, we will see the same behavior.
Girish,
My test team is using the function "Copy Change". At that point the change that is being copied is closed and all tasks completed. All tasks got an assigned group and assignee. In the first instance the group and assignee was selected manually not auto-populated.
They are then making a copy of the closed change including tasks. The assigned group and assignee are copied. When the change moves to "Scheduled" the task are in status Pending, status Reason Assignment.
There are a few issues here. I think the copy functionality should not include the assigned group and assignee. Or the should be an option to exclude the assignment data as part of the copy.
My issue is that the first task is not getting into status Assigned when the change moves to "Scheduled".
The assignee should not be copied over when task is being copied. At most the assignee group can be copied based on what the user selects. So this will be an enhancement/fix that needs to be done. In your case, after copy and when the assignment is a valid assignment, the task should not go to Pending status if the assignee is valid. We will try this at our end and if this is true, it is a defect that needs to be fixed.
Thanks, please let me know if I need report this through formal channels. Can you provide me with a issue number?
Hi Terje,
We apologize for the delay in getting back to you. While Girish or I can create a defect, that's not quite the same as an issue (which is easier for you to track).
If you'd prefer to have an issue number, please contact BMC Customer Support with your request.
Log in or register to comment.