Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-1864

Use (only) version start / end dates for chartboard "guideline" end points

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently the chartboard "guideline" end points default to the version start & end dates but the end points change (and guideline redrawn) if the start / end dates on the chart are varied.

      While a sprint should be timeboxed there are times when it is useful to show that the scheduled sprint end has not been met and the sprint activity continues beyond this scheduled end date.

      If the guideline start / end dates were fixed to the version start / end dates then this would permit showing the activity beyond the scheduled date rather than appearing to show the activity always being on time as the dates are changed on the chartboard

            [JSWSERVER-1864] Use (only) version start / end dates for chartboard "guideline" end points

            Michael Tokar added a comment -

            This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work.

            Regards,
            GreenHopper Team

            Michael Tokar added a comment - This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work. Regards, GreenHopper Team

            Bill Parker added a comment -

            to clarify:

            The current assumption is that the sprint will always end at the scheduled end date and unfinished issues rolled to a new sprint but it is just as valid in some situations to continue the sprint but still have the guideline fixed to the original start & end dates with effort continuing thereafter.

            Currently this cannot be displayed on the charts as changing the end date to encompass the later effort will also change the guideline end point.

            By fixing the guideline to the version start-end (as per the planning board RHS panel) then both situations can be accommodated.

            This might be accommodated in the proposed work on GHS-1947

            Bill Parker added a comment - to clarify: The current assumption is that the sprint will always end at the scheduled end date and unfinished issues rolled to a new sprint but it is just as valid in some situations to continue the sprint but still have the guideline fixed to the original start & end dates with effort continuing thereafter. Currently this cannot be displayed on the charts as changing the end date to encompass the later effort will also change the guideline end point. By fixing the guideline to the version start-end (as per the planning board RHS panel) then both situations can be accommodated. This might be accommodated in the proposed work on GHS-1947

              Unassigned Unassigned
              207741fc0d30 Bill Parker
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: