Have you guys ever noticed the message in the bottom right corner?

Hi Pedro,

Thanks for mention this. This helps a lot!!

Hi everyone,

Thank you very much for the feedback.

The upload information presented on the bottom-right side, illustrated above by Pedro Cardoso, seems to match the main use case reported in this thread, i.e. giving a time indication to the developer of the last publication. I concede that the visibility is not the best, but the need seems to be covered.

Occasionally there are also people showing interest in having concrete timestamps for each publish operation. I would like to dig a bit deeper and understand your use cases. Could you be more concrete on this? Why is this information useful?

Thank you once again for all your input.

Hi Pedro! Like João Rosado already mentioned before, times on the publish operations is useful because sometimes we end up publishing eSpaces multiple times since is not clear if the last version is published. Published is different of uploaded.

Another good reason is that timestamps on each publish step would bring to us more visibility about the amount of time taken to these operations.

Hey André,

Agree that distinguishing between upload and publish time might help developers.

Regarding the timestamp of each step, how you use this information? How could it be actionable?

I understand that, as a nice to have, you might wanted to know what is taking time but not sure if this would be reaaaaly helpful.

What do you think?

Cheers,

Vasco, in general it would help to troubleshoot performance issues on publishing a module, gathering metrics about the amount of time taken of each step. Is true that if the developer stay monitoring the progress bar and the publish tab on Service Studio (while publish occurs) it is possible to validate it somehow. But when publish finishes this information is lost. Furthermore, to know the exactly time of each step execution  is essential for report purposes. Is just to add the end operation time beside the publish info. In case of publishes made on past days, also show the date.

This is the kind of request that takes longer to argue against it or request that someone prove a useful use case than it does to implement, and implementing it and finding out no one needs it is painless to people. There's no good reason to NOT implement it.

My use case? To see if a publish is "stuck" on a particular step or not and needs someone to intervene on the server.

J.Ja

I think that this feature is so obviously useful that it hurts to have to see so many people explain why...

The uploaded timestamp is great, but uploaded isn't the same as compiled, deployed or published.

As some have already pointed out, having this info helps with debugging several situations, be it performance, be it whatever.

Guys,

The idea here is not to be a pain in the ### and force people to explain why. We just want to get more context and better understand your use cases.

In this case I think it is clear now, we will consider this in the near future ;)

Annnnd... it's been implemented! Thanks team!

J.Ja

Finally! Thanks!

O M G

Awesome! Thanks and congrats team!

Hi Vasco,

Almost perfect. It would be great if it also had the seconds.

Nice!!! Thanks guys...