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
Loving RocketChat so far, and have been testing it extensively for use in our organization. After using many solutions, both self hosted and commercial.. we have settled on Rocket Chat for it's community driven approach.
In light of that approach, I want to make one fairly important (IMO) feature request:
Please allow users to set their own time format, independent of the server setting. Some folks like 24hr time, some folks like AM/PM. It's not a big deal, but something I wish could be done. At the least use the system's time format.
I don't think I've missed this.. but if so, I do apologize for creating the issue.
The text was updated successfully, but these errors were encountered:
Closes#2922Closes#4706
This PR adds a personal preference for what timestamp format to use:
![2018-06-16_21-26-48](https://user-images.githubusercontent.com/39674991/41501824-ffb5f034-71ab-11e8-813e-8a2c724fc84b.png)
**Default** uses the timestamp formats (usually `LT` and `LLL`) defined in admin settings.
**12-hour** uses a 12-hour format (`6:30 PM` or `January 3, 2018 6:30 PM`)
**24-hour** uses a 24-hour format (`18:30` or `January 3, 2018 18:30`)
Your Rocket.Chat version: 0.43.0
Loving RocketChat so far, and have been testing it extensively for use in our organization. After using many solutions, both self hosted and commercial.. we have settled on Rocket Chat for it's community driven approach.
In light of that approach, I want to make one fairly important (IMO) feature request:
Please allow users to set their own time format, independent of the server setting. Some folks like 24hr time, some folks like AM/PM. It's not a big deal, but something I wish could be done. At the least use the system's time format.
I don't think I've missed this.. but if so, I do apologize for creating the issue.
The text was updated successfully, but these errors were encountered: