"Manage Child projects" Portal - Add last updated date to list of child projects

[hfloyd]

It would be awesome if there was some way to know when a child project was last updated from the Baseline. It might be the case that only a few projects are updated at a time (in batches, for instance) and having the "last updated from baseline" date next to the child project name would be helpful.

...Especially since sometimes the progress isn't properly updated in the UI of the page when doing an update. It can be difficult to know if the individual child project updates succeeded/completed or not.

Related:

• https://github.com/umbraco/Umbraco.Cloud.Issues/issues/122
• https://github.com/umbraco/Umbraco.Cloud.Issues/issues/99

[hfloyd]

I was thinking about this and it occurred to me that perhaps the date could be added to the child site's web.config after the update/deployment completes, something like:

<add key="Umbraco.Deploy.LastUpdatedFromBaseline" value="2019-12-11 11:34:35 AM" /> (or in whatever format makes sense)

The advantage is that the data could then also be available to the website itself - to include "version" info in Error logs, or ever run certain code conditionally, if needed for some update reason.

[nul800sebastiaan]

Thanks for the feature request @hfloyd - we had a chat at HQ and this makes good sense to use. We'll bundle a few requests for baseline improvements and put them on the list of future things we want to work on. I believe we do have data on when an update from baseline was done last, so we won't need to hack it into an appSetting.

This doesn't fit in our sprints for the next few weeks but we have put it on the list with ideas for future sprints. We regularly review this list of sprint ideas to see when it makes sense to pick it up. Once we know we'll start building this feature we'll update this issue again. 👍

[umbrabot]

Hiya @hfloyd,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

[hfloyd]

@umbrabot still relevant

Not yet implemented

[umbrabot]

Hiya @hfloyd,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

[greystate]

Just casting a vote here for something that would be very nice to see 👍