Affects Bundle Custom Field doesn't page results, performance implications

Description

When viewing the results for the Affects Bundle Custom Field (and presumably also the Fixed In Bundle Custom Field), the results are not paged.

This has client-side implications where one of our Affects Versions belongs to hundreds (or thousands) of bundles.

At worst, the client lags due to waiting on network or server resources. At best, the client has to scroll quite a lot.

I'd post a picture but it would contain a lot of internal information. But as an example, one of our component versions belongs up to nearly 2400 bundles. Displayed in the browser, it spans 3 screen heights (15 inch Mac Pro).

Environment

self-hosted, AWS

Activity

Show:
Deniz Oğuz
March 20, 2020, 5:49 PM

Do you see 2400 bundle name in the highlighted area of below issue section ?


Adding pagination for a custom field is not something I want to do. May be we can only show first 5 bundles or something like that?

Christina Jenks
March 23, 2020, 7:16 AM

That is correct – Short term that could work, however long term they’ll still want to be able to view the full list in some way.

Assignee

Deniz Oğuz

Reporter

Christina Jenks

Labels

None

Source

None

Jira Version

Database Type/Version

PostgreSQL 9.4

Browser Type/Version

Chrome / 80.0.3987.132

Affects versions

Priority

Major
Configure