Uploaded image for project: 'ONE'
  1. ONE
  2. ONE-30378

Resources module: Performance improvements of loading tasks for "Show overall assignment"

    XMLWordPrintable

    Details

    • Team:
      Resources
    • Product:
      BigPicture, BigGantt
    • Host platform:
      JIRA server, JIRA cloud
    • Customer Rank:
      6
    • Hide Fields:
      $i18n.getText("admin.common.words.hide")
      $i18n.getText("admin.common.words.show")
      var cfToHide1 = document.getElementById("rowForcustomfield_18501"); if(cfToHide1){cfToHide1.style.display="none";} var cfToHide2 = document.getElementById("rowForcustomfield_18502"); if(cfToHide2){cfToHide2.style.display="none";} var cfToHide3 = document.getElementById("rowForcustomfield_19700"); if(cfToHide3){cfToHide3.style.display="none";} var cfToHide4 = document.getElementById("rowForcustomfield_18400"); if(cfToHide4){cfToHide4.style.display="none";}
    • Sprint:
      Sprint 2020/28, Sprint 2021/01
    • Program Increment:
      PI2021/1
    • Story Points:
      1
    • On Roadmap:
      No
    • Hide Fields Design:
      $i18n.getText("admin.common.words.hide")
      $i18n.getText("admin.common.words.show")
      var cfToHide1 = document.getElementById("rowForcustomfield_18501"); if(cfToHide1){cfToHide1.style.display="none";} var cfToHide2 = document.getElementById("rowForcustomfield_18807"); if(cfToHide2){cfToHide2.style.display="none";} var cfToHide3 = document.getElementById("rowForcustomfield_19700"); if(cfToHide3){cfToHide3.style.display="none";} var cfToHide4 = document.getElementById("rowForcustomfield_18400"); if(cfToHide4){cfToHide4.style.display="none";}

      Description

      Performance of loading tasks when "Show overall assignment" option is active may increase up to 40% - depending on number of Individuals / Teams visible on the screen and their tasks distribution.

       

      Together with above performance improvement, a small change in "Show overall assignment" for Teams view is introduced. It is best to explain this change using an example:

      • Let's assume that there is a Team named Alpha with code ALPHA, which is created and allocated only to Box PROG-1
      • Let's assume that there is a Task with key T-1, which is assigned to Team with code ALPHA (in its labels or single select field, depending on configuration), but it is in scope of Box AGILE-1 only (and not PROG-1)
      • Prior to aforementioned change, when enabling "Show overall assignment" for Teams view in PROG-1, there was a check for each task whether it belongs to any of Boxes that the team belongs to
        • So in above situation, although task T-1 was assigned to team with code ALPHA, application spotted that the task and the team have no common Box. As a result, application did not include this task in the view (and in team's workload as well)
        • The only way to make task T-1 visible, was to assign team Alpha to AGILE-1 or to include task T-1 in the scope of PROG-1 - resulting in task and team having one Box in common
      • With aforementioned change, this check no longer exists. As a result, task T-1 will appear in Resources module of PROG-1 no matter whether this task belongs to any Box that the team Alpha belongs to, or not.

      This check was removed from the app mainly because of performance reasons, as having to check for each task and for each team whether they have any Box in common was very time consuming.

        Attachments

          Issue Links

            People

            Assignee:
            lukasz.panek Łukasz Panek
            Reporter:
            lukasz.panek Łukasz Panek
            SoftwarePlant People involved:
            jakub.zygmunt Jakub Zygmunt , tomasz.jaskiewicz Tomasz Jaśkiewicz , system.jenkins Jenkins , bartosz.drazewski Bartosz Drążewski , martyna.turowska Martyna Turowska , pawel.guz Pawel Guz , grzegorz.duzy Grzegorz Duży , bartlomiej.janczak Bartłomiej Jańczak , system.gerrit Gerrit , lukasz.panek Łukasz Panek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Start date:
              End date: