Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show full timestamps in UI #2395

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

philmcmahon
Copy link
Contributor

Status

Ready for review

Description

This modifies the securedrop UI so that it shows a timestamp rather than just the date for the most recent source message. This addresses these issues (which also include a fair bit of relevant prior discussion):

At the guardian, timestamps are extremely valuable when working in a multi user environment and helping to coordinate work.

It looks like this:

415217006-68b7508c-06f2-4817-9664-e1219915ffab

Test Plan

I've tested this on my development qubes workstation

Checklist

If these changes modify code paths involving cryptography, the opening of files in VMs or network (via the RPC service) traffic, Qubes testing in the staging environment is required. For fine tuning of the graphical user interface, testing in any environment in Qubes is required. Please check as applicable:

  • I have tested these changes in the appropriate Qubes environment
  • I do not have an appropriate Qubes OS workstation set up (the reviewer will need to test these changes)
  • These changes should not need testing in Qubes

If these changes add or remove files other than client code, the AppArmor profile may need to be updated. Please check as applicable:

  • I have updated the AppArmor profile
  • No update to the AppArmor profile is required for these changes
  • I don't know and would appreciate guidance

If these changes modify the database schema, you should include a database migration. Please check as applicable:

  • I have written a migration and upgraded a test database based on main and confirmed that the migration is self-contained and applies cleanly
  • I have written a migration but have not upgraded a test database based on main and would like the reviewer to do so
  • I need help writing a database migration
  • No database schema changes are needed

@philmcmahon philmcmahon requested a review from a team as a code owner February 20, 2025 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant