Grant
August 16, 2025, 4:10am
3
Hi @NielsKlazenga ,
Thank you again for your report!
In the Specify 7.11.1 update , we’ve resolved the issue with ‘Day’ and ‘Month’ fields erroneously reporting 1!
We are working on a solution to the issue with time not being displayed for TimestampCreated and TimestampModified now, which I expect to arrive relatively soon:
issue-641-time ← issue-477
opened 03:58AM - 16 Aug 25 UTC
Fixes #477, built on top of the fix for #641 since we use the back end timezone … for timestamps
This PR puts the "time" in "timestamp" 🕐
**Before:**
<img width="1585" height="581" alt="image" src="https://github.com/user-attachments/assets/3f8360ad-6f05-4692-b8ea-9fd5b46e355f" />
**After:**
<img width="1582" height="709" alt="image" src="https://github.com/user-attachments/assets/f6ef3600-5ec1-4e50-8bec-9c01846ba174" />
### Checklist
- [X] Self-review the PR after opening it to make sure the changes look good and
self-explanatory (or properly documented)
- [ ] Add relevant issue to release milestone
- [ ] Add pr to documentation list
- [ ] Add automated tests
- [ ] Add a reverse migration if a migration is present in the PR
### Testing instructions
- [ ] Query on `TimestampCreated` and `TimestampModified`
- [ ] Verify that the time is now displayed in the query results
- [ ] Verify that sorting both ascending and descending order works appropriately
- [ ] Test all supported query operators and verify the behavior is consistent