-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Improve the "Delete" experience on the Bulk Import Added Repositories page
-
False
-
-
False
-
RHIDP-4171Improve user experience on the bulk import pages
-
To Do
-
RHIDP-4171 - Improve user experience on the bulk import pages
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 50% In Progress, 50% Done
-
-
EPIC Goal
What are we trying to solve here?
Repositories might be added to Developer Hub from various sources (like statically in an app-config file or dynamically when enabling GitHub discovery). By design, the bulk import plugin will only track repositories that are accessible from the configured GitHub integrations.
However, deleting a repository from the Bulk Imports listing page may not work if the repository was discovered by the GitHub discovery plugin or if it was added via an app-config file.
Background/Feature Origin
https://issues.redhat.com/browse/RHIDP-4171
Why is this important?
This may cause users to mistakenly believe that the delete functionality is not working.
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>