-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Deprecate "Verified" Badge and Introduce Transparent Plugin Support Indicators
-
S
-
False
-
-
False
-
Done
-
RHIDP-7909 - Removing "Verified" And Improving Transparency In The Extensions Catalog
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
-
Feature
-
-
EPIC Goal
Deprecate the ambiguous “Verified” plugin status and replace it with a transparent, tiered support model (GA, TP, DP) aligned with Red Hat standards—improving clarity, customer trust, and internal consistency across the Extensions Catalog.
Background/Feature Origin
The “Verified” badge has become an ambiguous indicator. Unlike “Certified” (partner-specific) or “Custom” (customer-internal), “Verified” doesn’t convey specific meaning or guarantee of support. With Red Hat Developer Hub (RHDH) maturing, there's a need to
increase alignment with broader Red Hat terminology (GA, TP, DP).
Why is this important?
- Enhances customer understanding and confidence in choosing the right plugins.
- Aligns the product with Red Hat standards and terminology.
Acceptance Criteria
1. Remove “Verified” badge and related content from the UI
- Remove all instances of the “Verified” checkmark lozenge and any associated text.Affects plugin list views and detail pages in the Extensions Catalog.
2. Update plugin metadata
- Update plugin metadata to include the correct Supported By and Release Status data.
- Metadata Already there : Author, Tags, Category, Backstage version supported
- All plugins including plugins being added as new plugins in this release cycle (see RHIDP-6899) must have accurate metadata ().
2. Add Support Status fields in plugin details
- Add two new fields on plugin's detail page figma :
- Release Status: Displays one of the following values: "Generally Available", "Technology Preview", "Developer Preview".
- Supported By: Displays one of the following values: "Red Hat", a specific partner or customer name (e.g., "MegaCorp Inc."), or "Backstage Community"
3. Implement “GA” Badge (figma)
- Show green badge only when:
- Release Status is Generally Available and
- Supported By is Red Hat.
- Add tooltip `Generally available and supported by Red Hat`.
4. Preserve existing badges
- Certified (Purple): Used for Red Hat partner plugins – remains unchanged.
- Custom (Yellow): Used for customer-developed plugins – remains unchanged.
5. Display extended metadata on plugin pages (figma)
- Enhance the plugin detail view to include:
- `Author`, `Tags`, `Category`, `Backstage version supported`, `Support Status`.
6. Update Support Type Filter to Support Status
- Update Filter Name
- Update Support status filter status value according to figma ie Icon, helper text as well as adding all the options.
7. Explain status on details page
- On hovering over status sentence explaining status meaning should be visible like given in figma.
8. Add details to 1.8 release notes
- relates to
-
RHDHBUGS-2124 Fix Test: Verify community plugin badge in extensions test
-
- Closed
-