| PPM Field Type |
Sync Direction |
JIRA Field Type |
Notes |
| Portfolio |
Bi-directional |
String
List
|
- The Portfolio field is available for PPM request type that uses a request header type that includes either of the following field groups: PFM - Proposal, PFM - Project, or PFM - Asset.
- Value mapping is supported when matching with a List field in Jira.
|
|
Text
Field
Text Area
|
From PPM to JIRA
|
User
Picker (single user)
User Picker (multiple users)
|
- Sync successfully when PPM passes emails address, username, or full name existing in JIRA.
- Only support passing a single user each time.
|
|
Text
Field
Text Area
|
From JIRA to PPM
|
User
Picker (single user)
User Picker (multiple users)
|
Use email address to find matching user in PPM.
- If the user exists in PPM, the PPM field displays the user's full name in PPM.
- If the user does no exist in PPM, the PPM field displays user's full name in JIRA.
Multiple users are separated by ";".
|
|
User
User List
|
From PPM to JIRA
|
Text
Field (multi-line)
Text Field (single line)
|
Users are synced to JIRA by full names, separated by ";". |
|
User
User
List
|
From JIRA to PPM
|
Text
Field (multi-line)
Text Field (single line)
|
Sync successfully when JIRA passes full names or usernames existing in PPM.
When JIRA passes a full name or username not existing in PPM, the PPM field keeps the old value.
Support sync of multiple users per time.
|
|
User
User
List
|
From PPM to JIRA
|
User
Picker (single user)
User Picker (multiple users)
|
Sync
successfully when PPM passes email address or username existing in JIRA.
When PPM passes an email address or username not existing in JIRA, the JIRA field is cleared.
If PPM "User List" field type is mapped with JIRA "User Picker (single user)" field type, a random user that exists in JIRA is synced to JIRA.
|
|
User
User List
|
From JIRA to PPM
|
User
Picker (single user)
User Picker (multiple users)
|
Sync successfully when JIRA passes email address existing in PPM.
When JIRA passes an email address not existing in PPM, the PPM field is cleared.
If JIRA "User Picker (multiple users)" field type is mapped with PPM "User" field, a random user that exists in PPM is synced to PPM.
|
|
Text
Field
Text Area
|
Bi-directional
|
Text
Field (multi-line)
Text Field (single line)
|
PPM page will issue an error if PPM passes text that exceeds
the JIRA field length.
The PPM field content will be truncated if JIRA
passes text that exceeds PPM field length.
|
|
Auto Complete List
Drop Down List
|
Bi-directional
|
Select
List (multiple choices)
Select List (single choice)
|
If a multi-select field is mapped with a single-select field, the single-select field value is randomly mapped to one value in the multi-select field.
|
|
Auto Complete List (SQL-Custom)
Drop Down List (SQL-Custom)
|
Bi-directional
|
Select List (single
choice) |
Sync successfully when both side pass values existing in the other side.
PPM page will error out If PPM passes a value not existing in JIRA.
Only support sync of a single value per time.
|
|
Auto Complete List
Drop Down List
|
From PPM to JIRA
|
Text
Field (multi-line)
Text Field (single line)
|
Multiple values are separated by ";". |
|
Auto Complete List (SQL-Custom)
Drop Down List (SQL-Custom)
|
From PPM to JIRA
|
Text
Field (multi-line)
Text Field (single line)
|
Multiple values are separated by ";". |
|
Text
Field
Text Area
|
From JIRA to PPM
|
Select
List (multiple choices)
Select List (single choice) |
Multiple values are separated by ";". |
| Date |
Bi-directional |
Date Picker |
Available from v26.2: Supported for Jira field mapping when integrating PPM requests with Jira issues (Jira Cloud and Jira Server). Map date fields such as due dates, target completion dates, and start dates.
|