SDK package work item data for Engagement Experience PowerBI Report

[ladonnaq]

Issue: Azure Devops work items that have a "parent-child" relationship can be ingested into PowerBI via Analytics and it is straightforward to obtain data values while preserving the data integrity. It is not possible to preserve the data integrity for Azure Devos work items that have a "related" relationship. Therefore, the SDK data cannot be retrieved and mapped to the correct release plan.

History: In the original engagement model data model design the API Spec and SDK package work items were children of the release plan work item. However, engineering had to integrate with existing release tools, which the proposed data model would break. So the SDK packages are "related" to the release plan work item.

Requirement: Add SDK data fields to the release plan work item which will enable usage in the PowerBI report and preserve the data integrity.

Data requested by stakeholders:

• [x] Languages to be released
• [ ] SDK version
• [ ] SDK namespace
• [ ] Date SDK was released
• [x] Beta vs Stable
• [x] new initial (SDK)
• [ ] Arch Board GitHub issue link
• [ ] State of the SDK Package work item

[ladonnaq]

Fields that need to be added:

• [ ] SDK version
• [ ] SDK namespace
• [ ] Date SDK was released
• [ ] Arch Board GitHub issue link - possible, need to work out the details.
• [ ] State of the SDK Package work item
• [ ] new initial SDK - Leverage file that is in repos to determine if the product has existing SDKs.

[ladonnaq]

@maririos @praveenkuttappan - Where are we are the approach of determining the best way to get this data surfaced in the Release Plan work item so that Angelos can bring the data into the Engagement Experience Report for the Release tracking dashboards.