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

As a user, I would like the Cumulative Flow Diagram (CFD) to respect non-working days

    • 3
    • 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.

      The CFD does not make sense when it flatlines

            [JSWSERVER-3873] As a user, I would like the Cumulative Flow Diagram (CFD) to respect non-working days

            +1 would be very useful 

            Sebastien MEIFFREN added a comment - +1 would be very useful 

            +1. Please add this simple options. It makes our life much easier.

            Tomasz Urbański added a comment - +1. Please add this simple options. It makes our life much easier.

            Hassan Ali added a comment -

            It takes a while to notice that non working days are included (very visible after a Christmas vacation). Perhaps warn people on the diagram so they know that this issue exist upfront until this defect is fixed.

            Hassan Ali added a comment - It takes a while to notice that non working days are included (very visible after a Christmas vacation). Perhaps warn people on the diagram so they know that this issue exist upfront until this defect is fixed.

            EdM added a comment -

            I'd ask this be prioritized as well; but I'll bet money this will be open (or closed as won't fix) in 2020.

            EdM added a comment - I'd ask this be prioritized as well; but I'll bet money this will be open (or closed as won't fix) in 2020.

            Agreed, not being able to exclude non working days skews the data and makes it harder to do meaningful analysis.

            Michael Enright added a comment - Agreed, not being able to exclude non working days skews the data and makes it harder to do meaningful analysis.

            +1 for raising the priority up
            Chart should exclude week-ends and non-working days

            Pascal Rieux added a comment - +1 for raising the priority up Chart should exclude week-ends and non-working days

            I would also like to request that the priority of this issue be increased. This may be a story in terms of the new rapid boards, but I would be inclined to call it a bug and a regression for Greenhopper as a whole since moving from the classic boards.

            Tim Trinidad added a comment - I would also like to request that the priority of this issue be increased. This may be a story in terms of the new rapid boards, but I would be inclined to call it a bug and a regression for Greenhopper as a whole since moving from the classic boards.

            Since switching over To the new rapid boards from the classic version. Not having the ability to exclude weekends from a burndown is a pressing issue that is affecting my ability to produce effective reports for individual sprint iterations and the work our developers are complaining.

            Loss of basic functionality is a major step backwards and makes my job harder giving me more work.

            Scott Smallman added a comment - Since switching over To the new rapid boards from the classic version. Not having the ability to exclude weekends from a burndown is a pressing issue that is affecting my ability to produce effective reports for individual sprint iterations and the work our developers are complaining. Loss of basic functionality is a major step backwards and makes my job harder giving me more work.

            Please bring up the priority of this issue as this bugh throws off all our SCRUM calculations.

            Joe F. Lee added a comment - Please bring up the priority of this issue as this bugh throws off all our SCRUM calculations.

            I wonder why the priority is minor.

            I came from #GHS-5117

            At the moment, Rapid Boards are completely useless for SCRUM if weekends and non-working days are treated as normal working days. In other words, we pay a lot of money for a product we can not use!

            Markus Kalkbrenner added a comment - I wonder why the priority is minor. I came from # GHS-5117 At the moment, Rapid Boards are completely useless for SCRUM if weekends and non-working days are treated as normal working days. In other words, we pay a lot of money for a product we can not use!

              Unassigned Unassigned
              sclowes Shaun Clowes (Inactive)
              Votes:
              91 Vote for this issue
              Watchers:
              53 Start watching this issue

                Created:
                Updated: