Problem
The customer needs to configure PPM Express to show Work Item statuses as 'Done' when these items have a state of 'In Service' in Azure DevOps (ADO). However, they are facing challenges due to the need for additional mappings between Azure DevOps states and PPM Express statuses. There are complexities involved as separate transformation rules are required for each Work Item type, and there are concerns about how automatic task status calculation in PPM Express affects this process.
Solution
To resolve the customer's issue, the following steps were recommended by the PPM Express Support Team:
- Disable the automatic calculation of 'Task Statuses' for the project in question.
- Conduct the necessary mapping of Work Item types in the Azure DevOps connection settings.
- Add a new Transformation Rule to map the 'In Service' state in Azure DevOps to the 'Done' status in PPM Express.
- Save the Transformation Rule and subsequent mapping configurations.
These steps need to be repeated for each Work Item type to ensure proper mapping and avoid 'N/A' statuses where no mapping exists.
Additionally, they suggested that:
- The customer should also consider mapping common Azure DevOps states like 'Proposed', 'Active', 'Research', 'Blocked', 'Build', and 'QA' to one of the five available PPM Express statuses.
- Disabling automatic calculation of 'Task Statuses' is necessary; otherwise, PPM Express will ignore the mappings and base the status on the default logic tied to the current date, due dates, and threshold values.
- To manage the 'Critical' status, customers may need to adjust the threshold values for the auto-calculation of Task Statuses within PPM Insights.
Finally, the customer was directed to a help article for more information on auto-calculation settings: PPM Insights Settings.
The customer was asked for an update, and eventually, they requested the closure of the ticket, which the support team confirmed and carried out.