[MGNLUI-5999] Improve responsivity of the pulse when working with large amount of tasks Created: 26/Jun/20  Updated: 03/Jun/21

Status: Open
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.6.12, 5.7.7
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to TASKMGMT-41 Pulse performance slows down as numbe... Closed
is related to TASKMGMT-43 Expose a method to archive all tasks ... Open
is related to TASKMGMT-42 Expose a method to retrieve all tasks... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

This ticket is to collect the UI improvements for the Pulse for customers that use tasks heavily.

  • TASKMGMT-41: introduces a targeted indexing configuration for the tasks workspace. This will have an impact on all queries ran on the task workspace.
  • TASKMGMT-42: introduces a new method for getting all tasks assigned to a given user to help speed up refreshing the Pulse view.
  • TASKMGMT-43: introduces a new method for archiving all tasks for a user

Changes made to the TaskListPresenter

  • Refactor updateView() to make one query for determining task counts. This method is called so much that making 4 separate queries is just too much overhead to be efficient. See MGNLUI-4335.
  • Add an extra line of debug to updateView() to detect bottlenecks.
  • Introduce a new configuration parameter for resolved tasks. By default it's set to 100 but can be adjusted higher. Also can be set to negative to remove the check entirely. The idea is to auto archive the tasks once the threshold is reached.

Generated at Mon Feb 12 09:32:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.