Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Tree - Performance Issues when Expanding All Files #4986

Open
KyEggleston opened this issue Jan 9, 2024 · 0 comments
Open

Document Tree - Performance Issues when Expanding All Files #4986

KyEggleston opened this issue Jan 9, 2024 · 0 comments
Labels
bug Something isn't working low priority

Comments

@KyEggleston
Copy link

KyEggleston commented Jan 9, 2024

Describe the bug in current situation
A clear and concise description of what the bug is.

In the Redaction App, when expanding all files in the package (i.e., to show all the pages) in the left pane / document tree, performance is significantly impacted on larger requests.

For example, on FOR-2023-30509, which contains 286 files, when selecting to expand all in the left pane / document tree, performance is impacted when trying to perform further actions in the left pane / document tree.

Selecting pages, apply page flags, expanding or collapsing files all take seconds to respond.

This ticket is to investigate performance related challenges/improvements related to this feature.

Link bug to the User Story

#4432

Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.

Low

Chance of Occurring (high/medium/low/very low)

Medium

Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?

PROD and TEST

Steps to Reproduce
Steps to reproduce the behavior:

  1. Go to FOR-2023-30509 in the Redaction App
  2. Expand all files in the left pane / document tree
  3. Click a page in the package, or right click to bring up the page flag context menu
  4. See performance issues

Actual/ observed behaviour/ results

Performance impacted when expanding all files

Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.

Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

@KyEggleston KyEggleston added bug Something isn't working low priority labels Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low priority
Projects
None yet
Development

No branches or pull requests

1 participant