MicrosoftDocs / quantum-api

Creative Commons Attribution 4.0 International
9 stars 16 forks source link

[METADATA UPDATE][Merge by 2024-01-27] Global reporting metadata update #109

Closed learn-build-service-prod[bot] closed 7 months ago

learn-build-service-prod[bot] commented 7 months ago

A Pull Request has been made from the Learn Platform's Metadata Management System. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about the purpose of these metadata updates, please contact docs-allowlist-mgmt@microsoft.com. If you are not the correct contact for this content and repository, please notify Metadata-Management@microsoft.com.

If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Please notify Metadata-Management@microsoft.com if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#932729 Remove ms.prod = qsharp. Replaced by ms.service = qsharp

Why do we make metadata updates? The C+E Skilling Content Architecture team manages business-facing reporting taxonomies that enable analytics for OKR reporting and content portfolio management. Reporting taxonomy values populate metadata attributes.

We regularly review reporting taxonomies to ensure they are accurate, useful, and align to current business needs. Updates to these taxonomies and associated metadata make reports cleaner, easier to use, and more consistent.

How does this affect me? Once changes to reporting metadata are merged, standard dashboards and reports will reflect new values. You'll need to use new filter values in those dashboards and reports. If you have custom dashboards or Kusto queries, you might need to update those as well.

Frequently Asked Questions Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.

How can I revert a Pull Request that has been merged and created an unexpected issue? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.

learn-build-service-prod[bot] commented 7 months ago

Learn Build status updates of commit eb102b9:

:white_check_mark: Validation status: passed

File Status Preview URL Details
api/docfx.json :white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

prmerger-automator[bot] commented 7 months ago

PRMerger Results

Issue Description
Json File This PR contains json file(s).