EPIC Goal

There were some additional UI changes discussed during the bulk import feature refinement (RHIDP-6926), which were targeted as a stretch effort (primarily in RHIDP-8867). This is a placeholder to finish that and any other UI adjustments needed to finalize the implementation with design to simplify the end user experience and hopefully increase usage.

Design: https://www.figma.com/design/09Iltd57RiuqOtKWkjy8MH/Bulk-import?node-id=1503-4660&t=qcKZRLQPQ6Bc8J5p-1

Background/Feature Origin

Why is this important?

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

1. Clicking "Bulk import" in left navigation should take users directly to Import page
2. Page title should display "Bulk import"
3. Repository/Organization toggle buttons should not be displayed on Import page
4. Source Control Tool Configuration
       - Label should read "Source control tool" instead of "Approval tool"
       - Terminology should be properly translated in all supported languages
       - When only one source control tool is configured, the selection bar should be hidden
       - When only one source control tool is configured, the first step should be hidden from top info bar
       - When both GitHub and GitLab are configured, source control tool selection bar should be visible
       - Tooltip text should reflect "Source control tool" terminology (not "Approval tool")
5. Text in first and fourth items in top info section (Import to Red Hat Developer Hub section) should match design specifications exactly
6.  "Import" button should be disabled when no repositories are selected

7.   Empty state should be displayed when no repositories are available for import ( https://www.figma.com/design/09Iltd57RiuqOtKWkjy8MH/Bulk-import?node-id=1684-5347&t=VFr4yPeG0tUpMkQd-0 )
8.  "Missing configurations" page should be displayed when required configurations are missing ( https://www.figma.com/design/09Iltd57RiuqOtKWkjy8MH/Bulk-import?node-id=1503-9677&t=6nymz4e0TOMhbrDj-0 )
9. All states should follow design specifications (https://www.figma.com/design/09Iltd57RiuqOtKWkjy8MH/Bulk-import?node-id=1503-4660&t=m9FjZKSIbVwbvObF-0 )
10. Update unit and e2e tests

Stretch Goals (Optional/Future Considerations):: 

Note: Based on team discussions, these features may not be necessary since bulk import is typically a one-time admin setup task, not a regular user workflow.

Advanced "How does it work" Customization

• Admin users could edit the content of "How does it work" section via plugin YAML configuration
• Admin users could hide the entire section via configuration (beyond just collapse/expand)
• Custom icons or step content could be configurable
• User preference persistence (localStorage) for collapsed state