New issue
Advanced search Search tips

Issue 819783 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Bug tracker only has hour precision

Reported by jidanni@gmail.com, Mar 7 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
1. File a bug in this bug tracker
2. Later try to check the time that the bug or a comment was made

What is the expected behavior?
Can find out the the bug or comment was created at e.g., 21:36 .

What went wrong?
Can only find what approximate hour the bug or comment was created.

Did this work before? N/A 

Chrome version: 64.0.3282.119  Channel: n/a
OS Version: 
Flash Version:
 

Comment 1 by jidanni@gmail.com, Mar 7 2018

Why are minutes important? Well, then why are days important? Why not get rid of days?
Labels: Needs-Triage-M64
Cc: vamshi.kommuri@chromium.org
Components: UI
Labels: Triaged-ET
Status: WontFix (was: Unconfirmed)
Thanks for filing the issue!

This issue seems to be related to Bug tracker than Chrome. Hence requesting you to please file any bug tracker related issue here https://bugs.chromium.org/p/monorail/issues/entry . 


Sign in to add a comment