Details
-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
None
-
None
-
noticed in jira studio 2.2
Description
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
According to ISO 8601 and NEN 2772 the week that starts on monday the 16th of august should be week 33 this year.
Greenhopper states this is week 32.
Therefore the bug is: week numbers are wrong
This is a problem for me because: It makes it hard to communicate about week numbers when different tools use different week numbers. Outlook 2010 does it right, why can't we?
There may be more than one week standard out there that people want to use. Perhaps there is a good reason that Jira is currently not using the standards I mentioned. In that case this is not a bug but a feature request. In that case: please add a way for admins to choose the week numbering standard that they wish to follow.
to reproduce:
log in with admin rights for atleast one project
go to a project which you have rights for
click 'administer project'
click 'manage versions'
click the calendar for the 'release date'
compare week numbering with outlook 2010 and/or ISO 8601 and NEN 2772 numbering
Attachments
Issue Links
- is related to
-
JRASERVER-19946 Wrong calender week is displayed
- Gathering Impact
- relates to
-
JSWCLOUD-8075 week numbers in greenhopper are wrong
- Closed
-
CLOUD-3035 Update Look and Feel screen to mirror options in Jira 4.1.2
- Closed