That sounds like a bug, please contact support (https://support.atlassian.com) for assistance.

I'm confused. I have a hosted version of JIRA and recently upgraded Greenhopper to 6.1.3.2. I see the check box on the Sprint Burndown chart to exclude non-working days, but it seems to have no effect for me even after adding the four weekend days within our current sprint as non-working within the Greenhopper Admin page.

Am I missing something, do something wrong or is this still broken?

Hi All,

Just a quick update on this: both burndown and (GHS-6128) and control charts (GHS-5118) now support non-working days.

Many thanks

Tom Kotecki
Product Manager, GreenHopper

Hurray, Greenhopper 6.1.1 fixes this. Great work.
https://confluence.atlassian.com/display/GH/GreenHopper+6.1.1+Release+Notes#GreenHopper6.1.1ReleaseNotes-SpecifyyourNon-WorkingDays

Hi Everyone,

Thanks so much for your votes and comments on this feature request, we wanted to provide an update on the status.

We know there are features missing from the new Scrum and Kanban boards. We plan to deliver the burndown (GHS-6128) and control chart (GHS-5118) aspects of this story within the next 12 months.

Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!

Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed.

Cheers,
Shaun Clowes
GreenHopper Product Manager

Please restore ability to exclude weekends and other custom days as was available in classic. Thanks!

We need this issue solved. Please give us a real solution or a date to be solved. We need to evaluate if we continue with jira or change to another tool.

NOTE TO ALL SUPPORTERS OF THIS REQUEST

Stefan Kalhofer (SAP), Stefan Höhn (CSC) and myself (Software AG) will be having a phone conference with Nicholas Muldoon from Atlassian on Thursday.

If you wish to influence a change, TAKE YOUR CHANCE NOW in supporting us.

Please express yourself with respectable comments and votes on GHS-6754 (As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements) and related issues.

Many thanks in advance.

Rainer Mueck

Update:

The meeting took place on 29-Nov-2012. There are no concrete results yet, but there will be a follow-up meeting in one week. So please stay tuned for more updates to come.

I wonder why the priority of GHS-3873 is minor.

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!

Shaun, I support Kevin - this issue cause misleading in planning/controlling of the core of SCRUM framework and shall have at least High if not Immediate priority. It's not a good fashion working on cool new features when core is broken.

Just imagine the life of a SCRUM team that starts its 2 weeks sprint on Monday and has 1 holiday on the 2nd week of the sprint. The teams will be happily on track by the end of first week's Friday and will get completely distressed on Monday having no chances to catch up (remember there's also a holiday that RapidBoard displays as a working day). That team will get back to Classic Boards unless non-working days issue is fixed.