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

          Form Name

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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068759 ] New: JAC Suggestion Workflow 3 [ 3662278 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625517 ] New: JAC Suggestion Workflow [ 3068759 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326527 ] New: Confluence Workflow - Public Facing v4 [ 2625517 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043326 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326527 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031440 ] New: JIRA PM Feature Request Workflow v2 [ 2043326 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738698 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031440 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 1640000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 302444 ] New: JIRA PM Feature Request Workflow v2 [ 738698 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            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

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

                Created:
                Updated:
                Resolved: