Body
This article describes how to move project requests from one project application to another. Users must meet these criteria in order to move a project request:
- The user can edit the project request
- The user is a member of both project applications and has the View Project Request/Portfolio Planning pages permission in both applications.
- The user has the Move Project Requests permission in the project request's current application.
Users can move project requests between applications. Because many parts of a project request are defined within the application, significant parts of the request may be lost when moving it. It is not recommended to design workflows around routinely moving requests between applications. When you create a new application, consider which parts of the project requests will be lost or modified in the move in order to decide if ongoing requests should be moved into the new application, should be finished where they are. You should also consider whether the project request should be moved before it is converted to a project or after.
How to Move a Project Request
Follow these steps to move a project request form one application to another:
- On the TDWorkManagement project request detail page, select Actions > Move to Application.
- This will only be visible if the project request is editable in TDWorkManagement (i.e. it has been submitted) and the user meets these criteria:
- The user is able to edit the project request (either because they are the Evaluator or they have the Always Edit Requests permission).
- The user is a member of both the current project application and at least one other and has the View Project Request/Portfolio Planning pages permission in both applications.
- The user has the Move Project Requests permission in the current application.
- Select a Type for the moved project.
- Optionally, add a Comment.
- Click Move
What Happens when a Project is Moved?
When a project is moved, associated items on the project request are moved to the new application if possible, but some parts of the project request cannot be moved.
The following data will be permanently lost and the related section will be marked incomplete:
- Benefits
- Goals
- Organizational Risks
- Processes
- Scorecards
- Systems
- Workflow - project request workflows will be removed and the request will be put in the Submitted status
- Resources who do not have permission in the new application
Custom attribute values will be copied into a feed entry.
The project request and its related items will be moved to the new application, including:
- Feed
- Files
- Expenses
- Plans and Tasks
- Resources who have permission to the new application
- Returns
- Risk Register
- Role Forecasts
- Stakeholders
- Time Types
Risk statuses will be matched first by name, then by status class. If no match is available, the default status will be used.