Steps to replicate

      1. Create a new Scrum Board using a new Project that has no issues yet
      2. Create a new issue but do not fill the Original Estimate field
      3. Create a new Sprint and start the *Sprint
      4. Ensure that the Estimation Statistic is set to Original Time Estimate and use the Remaining Estimate and Time Spent for Time Tracking
      5. Switch to the Chart Mode of the Rapid Board and the Guideline is displayed as a hortizonal line dividing the Y-Axis and the value 0 is placed in the middle of the Y-Axis
      6. Switch to the Plan Mode and edit the issue to include an *Original Estimate of 20w
      7. Swicth back to the Chart Mode and it can be seen that the 0 value is in between the Y-Axis and the X-Axis and somehow, the Guideline does not appear on the chart. This is due to the fact that it overlaps the X-Axis, causing it not to be visible

        1. 1.JPG
          72 kB
          Ahmad Danial
        2. 2.JPG
          115 kB
          Ahmad Danial
        3. 3.JPG
          65 kB
          Ahmad Danial
        4. 4.JPG
          30 kB
          Ahmad Danial
        5. 5.JPG
          62 kB
          Ahmad Danial
        6. 6.JPG
          90 kB
          Ahmad Danial
        7. 7.JPG
          63 kB
          Ahmad Danial

            [JSWSERVER-6525] Burndown Chart Guideline overlaps the X-Axis of the chart

            Bugfix Automation Bot made changes -
            Minimum Version New: 6
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851267 ] New: JAC Bug Workflow v3 [ 2934402 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2543929 ] New: JAC Bug Workflow v2 [ 2851267 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549326 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2543929 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: Waiting New: Waiting affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909088 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549326 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747446 ] New: JIRA Bug Workflow w Kanban v6 [ 909088 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 446449 ] New: GreenHopper Kanban Workflow 20141014 [ 747446 ]

            Hi Shaun,

            Sorry if I was unclear. My point was that we don't put in any non-estimated issues in our sprints. Hence, there has always been XXX estimated hours when starting a sprint (Y != 0 at sprint start). And then, I see the guideline and everything is fine. However, after a few scope changes down the line, the guideline has broken several times.

            Benjamin

            Benjamin Golba added a comment - Hi Shaun, Sorry if I was unclear. My point was that we don't put in any non-estimated issues in our sprints. Hence, there has always been XXX estimated hours when starting a sprint (Y != 0 at sprint start). And then, I see the guideline and everything is fine. However, after a few scope changes down the line, the guideline has broken several times. Benjamin

            Hi benji,

            The beginning of the chart (which is also the top of the guideline) shows the estimate at the time the sprint was started. Since you applied the estimate after the sprint started the estimate at sprint start was zero. The line does stretch from start time, amount of hours to end time, 0 hours, but at the start time the estimate was 0 so the line is from (0,0) to (0,0).

            If you apply the estimates before starting the sprint the chart will work the way you expect it to.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi benji , The beginning of the chart (which is also the top of the guideline) shows the estimate at the time the sprint was started. Since you applied the estimate after the sprint started the estimate at sprint start was zero . The line does stretch from start time , amount of hours to end time , 0 hours, but at the start time the estimate was 0 so the line is from (0,0) to (0,0). If you apply the estimates before starting the sprint the chart will work the way you expect it to. Thanks, Shaun

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: