• Type: Bug
• Resolution: Tracked Elsewhere
• Priority: Medium (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: None
• Component/s: None
• Labels:

  • greenhopper
  • usability
  • —triage
  • —verify
• Environment:

  noticed in jira studio 2.2

1. 

   date_picker.png

   34 kB

   12/Apr/2011 9:12 AM

[JSWSERVER-8075] week numbers in greenhopper are wrong

Owen made changes - 16/Oct/2018 1:08 AM

Workflow	Original: JAC Bug Workflow v2 [ 2850605 ]	New: JAC Bug Workflow v3 [ 2936532 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 25/Sep/2018 12:47 AM

Workflow

Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545309 ]

New: JAC Bug Workflow v2 [ 2850605 ]

Ignat (Inactive) made changes - 01/Feb/2018 12:08 PM

Workflow

Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549223 ]

New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545309 ]

jonah (Inactive) made changes - 02/Apr/2017 11:59 AM

Description

Original: 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

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-8075].   {panel} 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

jonah (Inactive) made changes - 02/Apr/2017 11:59 AM

Link

New: This issue relates to JSWCLOUD-8075 [ JSWCLOUD-8075 ]

Owen made changes - 07/Jul/2016 7:04 AM

Workflow

Original: JIRA Bug Workflow w Kanban v6 [ 908738 ]

New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549223 ]

Oswaldo Hernandez (Inactive) made changes - 02/Jul/2015 12:53 AM

Workflow

Original: GreenHopper Kanban Workflow 20141014 [ 746985 ]

New: JIRA Bug Workflow w Kanban v6 [ 908738 ]

mtokar.adm made changes - 14/Oct/2014 12:00 AM

Workflow

Original: GreenHopper Kanban Workflow v2 [ 515301 ]

New: GreenHopper Kanban Workflow 20141014 [ 746985 ]

Martin (Inactive) made changes - 19/Nov/2013 4:13 AM

Resolution		New: Tracked Elsewhere [ 15 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Martin (Inactive) made changes - 19/Nov/2013 4:13 AM

Link

New: This issue is related to JRA-19946 [ JRA-19946 ]

Load more older history items