Move Project Request

Summary

Provides directions on moving project requests between different project applications within the UA Enterprise Service Management (ESM) system.

Body

Overview

Project Managers using the Enterprise Service Management (ESM) system to manage project requests can move requests between ESM project 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 thinking about moving a project request 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 another application, or 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.

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.

What materials do I need?

  • Internet access
  • Web browser
  • TDWorkManagement license
  • Access to both source and destination Project Applications

How to Move a Project Request

Follow these steps to move a project request form one application to another: 

  1. On the TDWorkManagement project request detail page, click 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 person meets these criteria: 
      • The person is able to edit the project request (either because they are the Evaluator or they have the Always Edit Requests permission).
      • The person 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 person has the Move Project Requests permission in the current application. 
  2. Select a Type for the moved project.
  3. Optionally, add a Comment. 
  4. Click Move.

What Happens when a Project Request 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.

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.

Details

Details

Article ID: 3023
Created
Wed 4/29/26 3:58 PM
Modified
Mon 5/4/26 12:07 PM