Transferring
Copying Tasks Between Projects
You can copy Tasks and their related assets from one Aphex Project into another Aphex Project.
If the copied Project Asset already exists within the destination Project, copied Tasks will be assigned to the existing Asset. Assets will be matched by Name. If the copied Project Asset doesn’t exist in the destination Project, it will be created and assigned to the relevant Tasks (permission dependant).
Properties transferred with Tasks can be customised each time a new batch of Tasks are copied.
Optional Task Properties
You can control if the following Task Properties will copied alongside your Tasks. If a property is not copied, the task will be allocated to the relevant default:
Asset or Property | Default |
---|---|
Duration/Dates | Today, |
Shift |
|
Status |
|
Calendar | Destination Project Default |
Subcontractor | None |
Labour | None |
Material | None |
Plant | None |
Location | None |
Work Area | None |
*Folders | None |
Package | None |
Blockers | None |
Tags | None |
Compulsory Task Properties
In addition to the optional properties, all copied Tasks will be created with the following properties:
Asset or Property | Rule |
---|---|
Task Name | Name of the Task |
Owner | All Copied Tasks will always be Owned by the User initiating the transfer |
Parent | Parent tasks will be copied with all of their subtasks |
External ID | External IDs from the source Project will always be added to the copied tasks in the destination Project |
Aphex Activity ID | A new Activity ID will be randomly generated in the destination Project NOT match the source Project |
Milestone | Milestone Tasks are always copied across as Milestones |
Notes | Notes on Tasks, Subtasks and Parents are copied across. Packages Notes will NOT be copied |
Internal Relationship Links | Internal links (links between selected tasks only) will be copied across. External links (links between selected tasks and non-selected tasks) will be ignored |
Discarded Properties
The following properties will always be discarded from the new, copied version of a Task:
Asset or Property | Rule |
---|---|
Assignees | Assignees will be blank |
Activity Log | Activity Log will not contain any history form the original Task |
Comments | Comments will be blank |
Documents | Documents will be blank |
Progress Updates | No progress updates recorded on the original Task will be copied to the new task |
Milestone Publish Version History | No Published Version History recorded on the original Milestone will be copied to the new Milestone |
Copying Tasks with Folders
If you choose to copy the Folder alongside a Task, the following rules apply:
Only the Folder paths associated with the chosen tasks will be copied
If a Folder has a Protected State, it will get copied with the State.
If the copied Folder matches an existing Folder on the destination Project, it will be overridden.
Depending on the destination Project's Permissions, Folders may not be created.
Copying Tasks with Blockers
If you choose to copy the Blocker alongside a Task, the following rules apply:
If the Blocker asset is new, the due date rules will be copied over
If the Blocker asset exists in the target project, the due date rule from the source project will be overridden on the asset
All due dates already set on Tasks will not be impacted
Depending on the destination Project's permissions, Blockers may not be created
Copying Tasks with Milestones
When copying a Milestone, the following rules apply:
Any Target Dates will be copied over to the new Milestones
No Published Version History recorded on the original Milestone will be copied to the new Milestone
Last updated