Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-98518

[Dashboard] View workload distribution for all assignees



      As an execution manager, I want to view a list of pending items for all assignees, so that I can learn how many items are under the responsibility for each person.

      This report is going to show how many pending tasks are assigned to users and classify the total pending items according to the SLA statuses Overdue and On Time. Note that these statuses are related to the processes items whose tasks are part of, and may not be related to the task itself.

      The filter and search features of the screen will be implement in separate tickets (LPS-103365 and LPS-103368).

      Acceptance Criteria

      • Users should be able to click on the "View all assignees" button, at the Workload by Assignee card, and be directed to the All Assignees report page;
      • The page should provide loading feedback when the table is being updated;
      • Consider as Overdue the total number of pending instances that breached one or more SLAs target times;
      • Consider as On Time the total number of pending instances that didn't breach any SLAs target times;
      • The sum of items Overdue and On Time can be smaller than the Total items (due to items that can be untracked);
      • The assignee image is retrieved from the global user profile picture;
      • If there are no assigned items, the table should display the specific empty state (as specified on Figma);
      • If the user update the report page that has an empty state and after that a new data arise the table must change from empty to populated;
      • If there is an unexpected error, the table should display the specific error state (as specified at the Components page on Figma);
      • When clicking on the username or item number, the user should be directed to the All Items page with the appropriate filters applied;

      Definitions of Done

      • Related tests created and passed successfully;
      • All Acceptance Criteria were passed;
      • Make sure that all system documentation were updated (if necessary);
      • Validated by QA, Product Designer and/or PM;
      • No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • Code with peer review completed.

      Design Deliverable:


          Issue Links



              matheus.xavier Matheus Xavier
              nathalia.moura Nathália Moura (Inactive)
              Engineering Assignee:
              Nathália Moura (Inactive)
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              0 Vote for this issue
              0 Start watching this issue




                  Version Package