Overview
Project Managers using the Enterprise Service Management (ESM) system to manage their projects can move projects between applications. Because many parts of a project are defined within the application, significant parts of the project may be lost when moving projects. It is not recommended to design workflows around routinely moving projects between applications. When you create a new application, consider which parts of the projects will be lost or modified in the move in order to decide if ongoing projects should be moved into the new application, or should be finished where they are.
Important
This feature will be available in an upcoming update to the Enterprise Service Management (ESM) system. This article should be considered a preview of features to come.
Warning!
In order to move projects from one project application to another, individuals must meet the following criteria in order to move a project:
- Person can manage the project (either directly or via the Manage All Projects or Mange Projects in My Portfolios permission)
- Person has access to both project applications
- Person has the Move Projects permissions in the project's current application.
Alternatively, an Enterprise Service Management ticket can be submitted to request an Enterprise Administrator transfer the ticket.
Be aware of the following!
Moving a project between ESM project applications will cause the following data to be permanently lost:
- Benefits
- Goals
- Organizational Risks
- Processes
- Scorecards
- Systems
- Document Workflows
- Resources and related schedules or resource requests for people who are not members of the new application, as well as resources selected for removal in the Move to Application menu.
- Removing a resource from the project while moving it is equivalent to manually removing the resource from the project from the Resources page.
- Custom Attributes – custom attribute values will be copied into a feed entry on the project and any project issues or risks that are moved.
What materials do I need?
- Internet access
- Web browser
- TDWorkManagement license
- Access to both source and destination Project Applications
How to Move a Project
Follow these steps to move a project form one application to another:
- On the project detail page, click Actions > Move to Application.
- This will only be visible for people who meet the criteria to move a project
- The user is able to manage the project.
- The user is a member of both the current project application and at least one other.
- The user has the Move Projects permission in the current application.
- Select a Type and Status for the moved project.
- Optionally, add a Comment or change the Health.
- In the Resources to Remove, optionally choose resources to remove from the project.
- Resources who are not members of the new application will automatically be removed when moving the project.
- Choose who to delegate schedules and tasks to for removed resources, and whether to delete or transfer those schedules and tasks.
- Click Move.
What Happens when a Project is Moved
When a project is moved, associated items on the project are moved to the new application if possible, but some parts of the project cannot be moved.
The following data will be permanently lost:
- Benefits
- Goals
- Organizational Risks
- Processes
- Scorecards
- Systems
- Document Workflows
- Resources and related schedules or resource requests for users who are not members of the new application, as well as resources selected for removal in the Move to Application menu.
- Removing a resource from the project while moving it is equivalent to manually removing the resource from the project from the Resources page.
- Custom Attributes – custom attribute values will be copied into a feed entry on the project and any project issues or risks that are moved.
The project and its related items will be moved to the new application, including:
- Announcements
- Calendar Events & Feeds
- Time & Expense entries
- Feed
- Issues and Issue Categories
- Links and Link Categories
- Plans and Tasks
- Resources, schedules and requests for users who are members of the new application
- Risks and Risk Categories
- Role Forecasts
- Stakeholders
Issue and Risk statuses will be matched first by name, then by status class. If no match is available, the default status will be used.
Need additional help or have issues
For support, requests may be submitted anytime using the appropriate Enterprise Service Management form. Requests generate a Ticket which will be worked in order received and urgency by IT Employees with the knowledge and permissions to assist with the request.
For immediate assistance please review the Contact Us page for the appropriate support group.