Request Tracker — Migration Support Overview
Role in migrations
- Staff (HD): supported as source.
- Contact (HD): supported as source.
- Ticket (HD): supported as source.
Field-level support migrating FROM Request Tracker (Ticket)
| Field | Supported |
| Requester | Yes |
| Company | No |
| Assignee | Yes |
| Group | No |
| Attachments | Yes |
| Comments | Yes |
| Tags | No such field in platform |
| Custom fields | Yes |
| CC | No |
| First Response Time | No |
| Created date | Yes |
| Updated date | Yes |
| Closed date | No |
Field-level support migrating FROM Request Tracker (Contact)
| Field | Supported |
| Tags | No such field in platform |
| Custom fields | Yes |
| Phone | No |
| Notes | No such field in platform |
Migration options available for Request Tracker
- Migrate the newest records first - applies to: source (Ticket)
- Select records for Demo - applies to: source (Ticket)
- Inline images in tickets - applies to: source (Ticket)
Request Tracker — Setup & How-To Guide
Request Tracker Migration Limitations
- Comments of type "Create" from the history are not read from Request Tracker. This can be read as a custom migration.
- The client must have the RT::Extension::REST2 plugin installed. Installation instructions: https://github.com/bestpractical/rt-extension-rest2
- Clients on version 5 have this module installed by default, so they can upgrade to version 5 — however, we advise against this.
Comments
0 comments
Please sign in to leave a comment.