Examples of automatically mapped fields: ALM or Jira defects
The following table lists some of the fields that are automatically mapped for new defect synchronization links. You can modify the mapping, but keep in mind that mandatory fields must be mapped to prevent errors.
Note: Fields that have been customized with modified list values in either endpoint are not automatically mapped.
ALM automatic mapping
ALM Octane field | Direction | ALM field |
---|---|---|
Attachments | Bidirectional | Attachments |
Author | Unidirectional | Detected By |
Closed on | Bidirectional | Closing Date |
Comments | Bidirectional | Comments |
Creation Time | Bidirectional | Detected on Date |
Description | Bidirectional | Description |
Detected By | Bidirectional | Detected By |
Detected in Release | Bidirectional | Detected in Release |
Name (mandatory) | Bidirectional | Summary |
Owner | Bidirectional | Assigned To |
Phase (mandatory) | Bidirectional | Status |
Priority | Bidirectional | Priority |
Release | Bidirectional | Target Release |
Severity | Bidirectional | Severity |
Sprint | Bidirectional | Target Cycle |
Story Points | Bidirectional | Estimated Fix Time |
Jira automatic mapping
ALM Octane field | Direction | Jira field |
---|---|---|
Attachments | Bidirectional | Attachments |
Author | Unidirectional | Reporter |
Closed on | Unidirectional | Resolved |
Comments | Bidirectional | Comment |
Creation Time | Unidirectional | Created |
Description | Bidirectional | Description |
Detected By | Bidirectional | Reporter |
Detected in Release | Bidirectional | Affects Version/s |
Name (mandatory) | Bidirectional | Summary |
Owner | Bidirectional | Assignee |
Phase (mandatory) | Bidirectional | Status |
Release | Bidirectional | Fix Version/s |
Priority | Bidirectional | Priority |