I like the idea of the page status but fail to see how it is any better than adding the status as text in the title of a page. At least with a text status in the title, I can filter pages and find those that have the text "needs review".
Multiple people hinted they want a report on page status but I haven't found a feature request for it. Does it exist?
We at Midori have been working one a Confluence app (for 2 years!) that provides Confluence page statusesmuch smarter than this relatively simplistic concept available in Confluence Cloud. Our app is actually the next-generation cloud version of our popular Data Center app that has been available for 15 years and used by many teams, from startups to giga-enterprises! We built all our prior experience and end-user feedback into the cloud version.
It addresses many critics mentioned in this thread like:
It displays counts and percentage, scales to large number of spaces/contents, can be filtered by content type (pages/blog posts/both), filtered by text matched against space key and space name. It also shows you the list of the contents in a given space and status.
Or, here is our status display above each page or blog, with analytics and immediate actions to update/confirm/expire/archive the page:
But there is much more! (And we are just at the beginning, our backlog is full of great ideas.)
As it is a macro with configurable parameters, you can add multiple instances with different parameters to a Confluence page and use that as dashboard.
You can't show a list of pages and status in the overview page. No idea why Atlassian has not implemented this feature.
In order to do this you need an addon like our Document Metadata for Confluence Cloud (paid, free trial) or one of the other paid addons on the marketplace.
Hi there, I'm using Confluence Cloud and although I can see the ability to set up statuses in the space settings, and even customize them, I just don't see the ability to set the status on any of the actual pages within my space! Am I going mad? Please let me know how to actually use the feature.
Here are screenshots of the space settings for Content Statuses and an example page with seemingly no option for actually setting a status.
If anybody can point me to where I'm going wrong, I'd be so grateful.
You need to open the page up for editing first. Then you can change the status at the top of the page.
By the way, the built-in status feature is limited to 5 centrally managed statuses. Will 5 statuses be sufficient for your workflows? If you are interested in a more professional, flexible, and purpose-built Confluence page status experience with reporting and automatically refreshing statuses, I recommend this comprehensive blog on the subject.
If you are considering Atlassian third-party apps to resolve your use case, you can look at Handy Macros for Confluence. It has a powerful Handy Page Status. It indicates the documentation status on top of the Confluence pages similar to the native status. But you get lots of advanced features in our macro:
create an unlimited number of status sets with unlimited options to fit in your every workflow
reuse status sets across spaces for consistency
track the history of page status changes in one click to immediately see the bottleneck
search for pages in a certain status by multiple criteria using our Page Status Report
create notifications for page statuses without updates for a long time using Confluence Automation
If you are interested, here's an article for your further reference.
Thank you @Levente Szabo _Midori_ - I eventually saw the ability to set the status in edit mode in a context menu. Was looking for it up at the top and side :-)
@Stephen McGeown That's great to hear. I'm still curious though: are 5 statuses enough for your content management workflow or to achieve what you want in terms of page status management?
I was happy when I discovered the option to add a status - and even create a custom status!
Next, I was utterly disappointed when I realized I cannot find all the pages I gave such a status! I want my users to mark a page with requires updating and then find those pages again!
Thanks @Kristian Klima , but manually adding all pages to "DB" - not an option. But I'm sure the DB will develop in the direction of actually being a DB and naturally support import and filter functionality. Until then, we'll mark pages as outdated and whoever sees it, sees it. That's already a small improvement.
Embed the "View single Content Property Macro" on the page, within your Page Properties template. Set the Content Property Name to "content-state-draft" and the JSON Path to "$.contentState.name".
The value then shows up in Page Properties reports.
It's not a very straightforward way to do this, and I would prefer to see it as a status badge, but it's working for me.
SUGGESTION: It would be great to show the status of a page in the tooltip that pops up when hovering over the page name in the sidebar. This way, we don't have to click on the page to view the status if we're trying to do a quick verification of multiple pages.
100 comments