Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

When an authorized user lands on the "Bulk Import" home page (Added Repositories), they might face some usability problems:

• they can view only the first 20 repositories (in alphabetical order) at most.
• the count of Added Repositories displayed might be wrong.
• deleting an Import job may not work if the repository was discovered by the GitHub discovery plugin or if it was added via an app-config file.

Also, the UI sends redundant requests to the backend and could benefit from caching. Otherwise, this could have an impact on the user experience as well.

These were reported as known issues in 1.3, but now, we want to improve this experience consistently through proper pagination and caching, providing a similar experience to what we have on all the other pages (Repositories, Organization, and Organization Repositories pages).

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

Consistent experience across all Bulk Import pages, where users might have a large amount of repositories imported.

Doing this would also allow users to have a better overview of the added repositories.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

• Pagination works as expected. Clicking on next/previous loads the appropriate data
• The count of added repositories is correct.
• Behavior of the Delete button is consistent.
• UI is optimized by caching API responses.

Out of Scope (Optional)

High-level list of items that are out of scope.

N/A

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

N/A

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

We would need to document this in the Release Notes.