• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: High High
    • 6.1.2
    • None
    • Classic - Boards
    • None

      1. When non working days are excluded from the calculation, there is currently no visual feedback on the chart showing where time was taken out.

      2. When non working days are included in the calculation, the fact that there is a weekend is interesting but a nice to have, because really it doesn't affect the calculation

      Currently 1. doesn't show the non working days and 2. shows the non working days which is the wrong way around. We should simply make the chart always show the non working days, as it is necessary in 1. and useful in 2.

      Comparing this to the burndown chart: there we never decide whether the non working days affect calculation, as they always do. The switch there is to include/exclude the non working days in the chart display, which as a result then adapts the x-axis scale. In the control chart however, we always show the full scale, which as a result should also show the non working days shaded.

            [JSWCLOUD-7072] Opinion: non working days shading should always be shown on the control chart

            Fixed on GHS-6616-epic-report

            JoanneA (Inactive) added a comment - Fixed on GHS-6616 -epic-report

            Cuantos caracteres soporta el campo Apellido?

            Prueba Sica added a comment - Cuantos caracteres soporta el campo Apellido?

            I don't think I quite get it.

            What we discussed with Jo was that if (1) non working days are being included the weekend should be shown unshaded (which also indicates that that time is being taken in to account in the calculations or (2) non working days are being excluded the weekend should be shaded (wich indicates that the time is being excluded from the calculations).

            The control chart is not the same as the burndown because the points don't represent an aggregate, they represent a single instance. If that single item was completed over the weekend hiding that fact obscures important data (that is not shown anywhere else because this chart doesn't have a time series table). Realistically, the point of the control chart is to measure cycle time (i.e the amount of time a customer can expect to wait), as a result weekends do really make a difference, this just lets people choose whether they want control chart in 'elapsed' or 'work day' time.

            The burndown chart doesn't change any calculation based on the weekends, it just chooses where to show the points when things happen over the weekend. The actual numbers (i.e time spent, remaining estimate) are identical regardless of the weekends.

            Shaun Clowes (Inactive) added a comment - I don't think I quite get it. What we discussed with Jo was that if (1) non working days are being included the weekend should be shown unshaded (which also indicates that that time is being taken in to account in the calculations or (2) non working days are being excluded the weekend should be shaded (wich indicates that the time is being excluded from the calculations). The control chart is not the same as the burndown because the points don't represent an aggregate, they represent a single instance. If that single item was completed over the weekend hiding that fact obscures important data (that is not shown anywhere else because this chart doesn't have a time series table). Realistically, the point of the control chart is to measure cycle time (i.e the amount of time a customer can expect to wait), as a result weekends do really make a difference, this just lets people choose whether they want control chart in 'elapsed' or 'work day' time. The burndown chart doesn't change any calculation based on the weekends, it just chooses where to show the points when things happen over the weekend. The actual numbers (i.e time spent, remaining estimate) are identical regardless of the weekends.

              Unassigned Unassigned
              miruflin Michael Ruflin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: