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
I'm not completely against, but I need to understand the usage of timestamps by Mistral users in general, and specifically in the Recent Executions screen.
What I'm concerned about:
What if a user started several executions- all with similar names (test1, test2, ...), or names are auto-generated. The timestamps help distinguish between executions. So marking them "today" may make it harder to tell.
What is the time-entity we should make the calculations on? createdAt? updatedAt?
We can think about showing relative time frames (like "3 hours ago", "22 minutes ago") for tasks created/updated(?) in the last 24 hours. We then may be incosistent with showing different time formats in the same screen (i.e. for some "today" or "3 hours ago" and for some "2018-04-23 10:20:30").
Answering 1: Hm.. This is a point. Maybe we can show a precise timestamp as a hint (when hovering on it)?
Answering 2: As a user, in the Recent Executions screen I'd prefer to see when an execution was created (created at).
Answering 3: It is indeed a good idea to me, yes (3 hr ago etc).
I think visually it'd be more convenient to see "today" instead of a full date. May be in other places too.
Not sure if you agree with me though.
The text was updated successfully, but these errors were encountered: