You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe it looks nice in "recent activity" but in the commit history, the "'x' days ago" information is not useful at all. Please put the timestamp there.
See in the screenshot below:
how not helpful at all is the information "2 days ago" and "3 days ago". More practical would have been to have the time, since the commits are grouped by date. Of course, after the date, one could extend with the text of how much time is that date in the past, but for single commits the timestamp is more helpful.
This is of course how GitHub works, but IMHO GitBucket should not "clone" the bugs too :).
Thank you.
The text was updated successfully, but these errors were encountered:
Elapsed time notation such as "2 days ago" is application internationalization technic. It's useful for global teams which have developers in different timezone. And you can confirm timestamp at tooltip as same as GitHub.
Make the other way round: put the timestamp in the list and the X days in the tooltip, since as the author mentions, the commits are already grouped by days, so that information is superfluous.
Maybe it looks nice in "recent activity" but in the commit history, the "'x' days ago" information is not useful at all. Please put the timestamp there.
See in the screenshot below:
how not helpful at all is the information "2 days ago" and "3 days ago". More practical would have been to have the time, since the commits are grouped by date. Of course, after the date, one could extend with the text of how much time is that date in the past, but for single commits the timestamp is more helpful.
This is of course how GitHub works, but IMHO GitBucket should not "clone" the bugs too :).
Thank you.
The text was updated successfully, but these errors were encountered: