Status Mapping
SD Elements can be made aware of the various statuses your Application Lifecycle Management (ALM) tools use for task completion. This is possible by mapping statuses you have set up in your ALM to the statuses that SD Elements uses, and vice-versa.
Once you create these mappings and sync your ALM to SD Elements (or vice-versa), SD Elements will better reflect the different states of your ALM’s workflow in task lists and reports.
For example, if you use a status called “Done” in your ALM, you can map it to the SD Elements status of “Complete”.
Status Mapping details
You can define which statuses in SD Elements are directly mapped to statuses in an ALM. In other words, you can define your ALM statuses against default SD Elements status meanings: Complete, Incomplete, and Not Applicable.
-
Custom ALM to SD Elements Status Mapping: The direct mapping between your ALM to SD Elements.
-
Custom SD Elements to ALM Status Mapping: The direct mapping between SD Elements to your ALM.
-
Closed Ticket Status: The status that is assigned to a task that becomes closed if it falls out of scope of your project. For example, when the project survey is changed and a task is no longer relevant to the project.
Legacy system connectors
System connectors created in versions of SD Elements prior to 4.19 are considered legacy system connectors. Syncs using these connectors will continue to work as before, but any updates to them will also require updating their status mappings as though they were a new system connector.
Project connections that use legacy system connectors can continue to be edited. While these project connections will continue to sync, update legacy system connectors for greater control of sync behavior.