Bug 3467 - RFE: inconsistent use of date formats in bugzilla screens (nit-picking category :)
RFE: inconsistent use of date formats in bugzilla screens (nit-picking catego...
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 1999-06-14 17:05 EDT by Eric Maryniak
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-04 14:41:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eric Maryniak 1999-06-14 17:05:54 EDT
This one really falls in the nit-picking category, and
I would have given it ultra-low priority if possible---
but being a fan of the ISO 8601 date format (CCYY-MM-DD,
eg. 1999-06-14), I could not help but notice the
inconsistent use of date formats in the several Bugzilla
screens, eg:
                                       Opened: 1999-05-03
------- Additional Comments ... 05/03/99 11:01 -------

Note that the first date seems OK, but is probably not,
ccyy-dd-mm in lieu of ccyy-mm-dd and the second does not
have cc (century). Furthermore, both dates are specific for
the US; Europe mostly uses dd-mm-ccyy notation. ISO 8601
has all sorts of nice qualities, such as millenium-
proofness, numerical and lexical ordering == date ordering
etc. Also note that in 2001 etc. dates will look strange,
what to bake of '02/03/01' etc., whereas 2001-02-03 is
You may want to check the ISO 8601 date standard at:

Comment 1 David Lawrence 2000-08-04 14:41:15 EDT
Good point. Changed to enhancement request.
Comment 2 Brent Fox 2002-06-04 15:02:27 EDT
I think the date format is more consistent now.

Note You need to log in before you can comment on or make changes to this bug.