Show if a feature is tracked in platform-status

[digitarald]

Previously talked @jensimmons & @JasonWeathersby about this:

platform-status references bugzilla ids, like in css-shapes.md.

To make sure all important features are publicly tracked in platform-status, devrel-dashboard could have an indicator for bugs that are already tracked as part of a feature in platform-status and link to it.

To close the loop, platform-status could use the DevRel: priority on a bug to highlight and rank features.

[callahad]

@digitarald I'm not familiar with platform-status's architecture... Can you suggest a good, client-side way for the DevRel dashboard to fetch that feature data?

[callahad]

Oh, and regarding surfacing the DevRel Priorities on platform-status: great idea for closing the loop, but I'm not sure we necessarily need to close that loop... those labels are mainly an indication of internal lobbying, rather than an engineering commitment, so we probably don't want them to be visible on the outward-facing platform-status dashboard.

[digitarald]

Can you suggest a good, client-side way for the DevRel dashboard to fetch that feature data?

I will expose bug numbers in the status API, to make that easier.

those labels are mainly an indication of internal lobbying, rather than an engineering commitment

The purpose is to present them as our perceived developer enthusiasm for the feature, not our own prioritization. For a similar indicator, see https://www.chromestatus.com/feature/5453022515691520 (Web Developers: Positive) on how chrome presents that data, probably also fed by their devrel team.