On many places in the platform (versions, publishing, conflict resolution, …) date/time for versions is displayed as “xx minutes ago”, “… days ago” and so on:
While this makes sense for minutes and seconds, maybe sometimes hours, it is very hard to work with when it is xx days or months ago. Yes it gives a very good indication but when I am looking if a certain model version has been uploaded or not, I need an exact date/time. Because “7 days ago” as in the example could be somewhere on 19/06/2026 (at the time of writing), but I received the IFC at 12:40 on the 19th.
Now it appears that in this particular case 7 days means that it was uploaded into Qonic on 20/06/2026 meaning it is (very likely at least) the correct latest version.
I guess it doesn’t hurt to show both the exact date/time and the current ‘days ago’ to combine the advantages of both.
Hi @Johan_De_Cock ,
The date is formatted as it is to keep it legible on a high level; if you need to know the specific time of a certain commit you can always hover your cursor over the date indicator to get the precise time stamp:
Hmm okay, that’s worth something at least 
Does it also work this way in the conflict resolution? At current I can’t check.
My main concern with something like this: the user has to know this ‘little trick’. It is very similar with the ‘copy’ command, holding shift while doing a translation.
If the software becomes full of this kind of small things (not necessarily undocumented, but hard to find out by yourself) it might in time affect the user experience.
This is not much different from classic tools, but in my view it is a bit contrary to the general UI/UX of Qonic that is very user-friendly and doesn’t require much training to get started and figure it out by yourself. But honestly, if I have to ask about how to do something in order to find out … that means none of my colleagues will ever know unless I tell them (and they’ll forget it even when I do 
).
