Under Community Review

This idea is similar to https://community.rws.com/ideas/tridion-ideas/i/tridion-sites-ideas/show-which-version-of-an-item-is-published

Although it is quite a good discussion is going in this thread so we will not close it as duplicate 

Data that will power all cool UI features related to version's publishing is currently not available in Content Manager Core

Let's collect more votes

Display Publish Date next to version number in version history

This enhancement request is from a Financial Services client in North America.

-- "To provide evidence related to record-keeping needs, the Compliance department would like to know when specific versions of a piece of content actually were published to the production site. Similar to the way we can review the history of every change made to a piece of content, we also would like to see the publish dates for each version."

If anyone else has similar need, please vote up the idea. 

Arijit Chowdhury

  • This would be of huge value for us -- it's great to have workflow history displaying when the content was edited, but we do not know when the versions actually were published, so if a piece of content is updated several times between being published to Active, it's about impossible to know when the updates actually appeared. Because of some legal or compliance issues, we are asked to detail specifically when the updates were published, but we generally are unable to.

    I also agree with your assessment of the dependency publishing relationships also being necessary. When a page is published and it also pulls the content components with it, we should have that publish action stamped on both the page and the component.

    But I can also think of this being added to the existing History pane, where we can see the object's updates and the publish date for each version.

  • This would be of huge value for us -- it's great to have workflow history displaying when the content was edited, but we do not know when the versions actually were published, so if a piece of content is updated several times between being published to Active, it's about impossible to know when the updates actually appeared. Because of some legal or compliance issues, we are asked to detail specifically when the updates were published, but we generally are unable to.

    I also agree with your assessment of the dependency publishing relationships also being necessary. When a page is published and it also pulls the content components with it, we should have that publish action stamped on both the page and the component.

    But I can also think of this being added to the existing History pane, where we can see the object's updates and the publish date for each version.

  • in reply to Alvin Reyes

    Hi ,

    Currently sites cmi overwrites the older publishing transaction showing only latest published transaction in the publishing queue.

    It will be good to have page like "where used" which shows "publishing history". The publishing history page should show:

    1. Timestamp of when published

    2. who published, user name

    3. Any dependency item which is published as part of current item publishing should also reflect the same publishing history.

    4. When a page is published, but as part of page publish, if components are also published, then those components should also show the time and user who published the page.

  • The main ask here seems like a straightforward request and would work for Pages and Component that are directly published. This gets challenging, though, with Component and Pages that use a piece of content, perhaps through several links.

    I think ideally, the request is also about knowing the publish date or status of the items that cause your item to appear on the site.

    Some examples:

    • When published, Pages can make their (statically) linked Components appear on the site, though the Components themselves aren't published
    • When published, a Component can make an image appear on the site, though the image itself doesn't have a published status
    • Components on a Page could change between Publishing events.

    once mentioned the idea of an "ultimate" where used, which is the Page or Component that may link to other items that eventually link to your item.

    Anyways, feel free to add more to the idea or perhaps consider a separate idea. I think the "ultimate" publish date or something like it would be needed to meet the requirement described. Wink