- Time Tracking Time Tracking is currently ON. The number of working hours per day is 9. The number of working days per week is 5. - General Configuration >> Non Working Days * 23/Mar/12Delete * 24/Mar/12Delete * 30/Mar/12Delete * 31/Mar/12Delete * 6/Apr/12Delete * 7/Apr/12Delete ************************************* GreenHopper Days Remaining at dashboard (9) Days Remaining Our spirnt information at Agile [Manage your dashboard with GreenHopper] >> Planning Board Parent: 1.19 Start Date: 20/Mar/12 End Date: 9/Apr/12 Release Date: 9/Apr/12 Please how can it get this number [9] ? the number must be [13] days not [9] ???????

I got it , i was supposed to change the number of working days per week from 5 to 7 in time tracking. Many thanks for your replies and effort with me

I don't understand what the confusion is - based on what you've got in Jira/Greenhopper, it's doing the right calculation, and I don't get why you keep saying it's wrong. It's probably me just not being able to grasp what I'm reading - could you explain why you are expecting non-working days to be included as working days? You've got 5 working days per week. Then you've got global non-working days (which you hadn't mentioned before), Then you've duplicated that at a project level. You need to remove the duplicated days to begin with (project administration level), and then talk to your admins about the global non-working days, as it sounds like they might be wrong.

The number of working hours per day is 9. The number of working days per week is 5. 2 non- working days + 5 working days = total 7 days our sprint 21 days = 3 weeks that's right ok until now we start sprint 20/03/2012 and it ends 09/04/2012 we cancel 2 non- working days for every week so non- working days will be 6 days 20/3 [15], 21/3 [14], 22/3 [13], 25/3 [12], 26/3 [11], 27/3 [10], 28/3 [9], 29/3 [8], 1/4 [7], 2/4 [6], 3/4 [5], 4/4 [4], 5/4 [3], 8/4 [2], 9/4 [1] Today 26 / 3 / 2012 >>>> The counter on dashboard now {8 Days Remaining} , the counter must be 26/3 [11 Days Remaining ] How can change this number from 8 to 11? Thanks for your replies and effort with me I got the reason we calculated non-working days twice the one time in General Configuration under GreenHopper, the second time in General Configuration on project's level How can i remove non-working days in General Configuration on project's level , Jira replys GreenHopper includes global non-working days, they can be modified below to meet specific project requirements. Note: Global non-working days can be modified by your JIRA Administrator. These dates will not be shown in your charts. All worklogs will be associated to the previous working day.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Days Remaining Error !!!!!!!!!!!!!! GreenHopper

haitham ahmed

- Time Tracking

Time Tracking is currently ON.
The number of working hours per day is 9.
The number of working days per week is 5.

- General Configuration >> Non Working Days

23/Mar/12Delete
24/Mar/12Delete
30/Mar/12Delete
31/Mar/12Delete
6/Apr/12Delete
7/Apr/12Delete

*************************************

GreenHopper Days Remaining at dashboard

(9) Days Remaining

Our spirnt information at Agile [Manage your dashboard with GreenHopper] >> Planning Board

Parent: 1.19

Start Date: 20/Mar/12

End Date: 9/Apr/12

Release Date: 9/Apr/12

Please how can it get this number [9] ? the number must be [13] days not [9] ???????

Accepted answers

All comments

Jakub Pierzchała

Hmm lets see, from my count:

1 - March 26th
2 - March 27th
3 - March 28th
4 - MArch 29th
5 - April 2nd (March 30th is a non working day)
6 - April 3rd
7 - April 4th
8 - April 5th
9 - April 9th (Release date, April 6th is a non working day)

Sums to 9 days, The bigger question is how did you get 13

Nic Brough -Adaptavist-

I'm not sure that my logic matches what Jira is doing, but I get 9 days too

Your sprint is set to cover three weeks, as below. My x's represent the days you've said "non working day", and the numbers are a counter.

20 Mar  Tue  1
21 Mar  Wed  2
22 Mar  Thu  3
23 Mar  Fri  non-working
24 Mar  Sat  non-working
25 Mar  Sun  4
26 Mar  Mon  5

27 Mar  Tue  6
28 Mar  Wed  7
29 Mar  Thu  8
30 Mar  Fri  non-working
31 Mar  Sat  non-working
 1 Apr  Sun  9
 2 Apr  Mon 10

3 Apr  Tue 11
 4 Apr  Wed 12
 5 Apr  Thu 13
 6 Apr  Fri  non-working
 7 Apr  Sat  non-working
 8 Apr  Sun 14
 9 Apr  Mon  15 Release

By my counting, you should therefore get 15 days.

However, your time-tracking says there are only 5 working days per week, so you need to remove 2 days per working week, which means you get 15 -6 = 9 days...

haitham ahmed

Thanks for your reply but

20 [1], 21[2], 22 [3], 25 [4], 26 [5], 27 [6], 28 [7], 29 [8], 1 [9], 2 [10], 3 [11], 4 [12], 5 [13], 8 [14], 9 [15]

20 [15], 21[14], 22 [13], 25 [12], 26 [11], 27 [10], 28 [9], 29 [8], 1 [7], 2 [6], 3 [5], 4 [4], 5 [3], 8 [2], 9 [1]

Although non wroking days calculated before 6 days

Today 26 / 3 / 2012 >>>> The counter on dashboard now {8} , the counter must be 26 [11] 11 Days

If you have answer for this issue please reply me

Nic Brough -Adaptavist-

I'm sorry, my formatting got all messed up when I posted the original. I've re-done it as a code block, which seems more clear.

I don't understand what you're asking now though. What I'm trying to point out is that you have told Jira that your sprint is 21 days long, with 6 non-working days, and 5 working days per week (i.e. 2 in 7 are also non-working). 21 - 6 - (3 * 2) = 9 days. Whatever order you do the two "2 days not working", you get 9 working days in the three weeks.

haitham ahmed

Our Sprint is 15 days without non working days

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud