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
This would be a short term improvement pending #538 - it would be helpful to see the time as well as the date in the sources list. Whilst we currently only have the date of last source activity, this is still fairly useful information.
I've noticed that this goes against the guidelines suggested in #332 - are we avoiding showing the time currently because it's not a true 'last updated' timestamp but only refers to the source?
Users may assume that the time refers to the 'last activity' rather than 'last source activity' - we could perhaps use a tooltip to make this clearer. I would argue that the existing date could lead to the same confusion, so adding the time would still be an improvement.
How would this affect the SecureDrop Workstation threat model?
User Stories
On the journalist interface we can see e.g. "20 minutes ago"; on the workstation it just shows the date (and not the year). Not having a time is a significant problem in a multi-user workflow because we know when whoever was last on shift did their job. Now we can't see if a "read" post was read during the course of that shift or not.
The text was updated successfully, but these errors were encountered:
Description
This would be a short term improvement pending #538 - it would be helpful to see the time as well as the date in the sources list. Whilst we currently only have the date of last source activity, this is still fairly useful information.
I've noticed that this goes against the guidelines suggested in #332 - are we avoiding showing the time currently because it's not a true 'last updated' timestamp but only refers to the source?
I started having a stab at this (https://github.com/guardian/securedrop-client/tree/show-last-updated-time) but having found the issues above it looks like more discussion would make sense before persevering. Here's what the sources list could look like:
How will this impact SecureDrop users?
Users may assume that the time refers to the 'last activity' rather than 'last source activity' - we could perhaps use a tooltip to make this clearer. I would argue that the existing date could lead to the same confusion, so adding the time would still be an improvement.
How would this affect the SecureDrop Workstation threat model?
User Stories
On the journalist interface we can see e.g. "20 minutes ago"; on the workstation it just shows the date (and not the year). Not having a time is a significant problem in a multi-user workflow because we know when whoever was last on shift did their job. Now we can't see if a "read" post was read during the course of that shift or not.
The text was updated successfully, but these errors were encountered: