Is there a way of defining a page status without using an add-on?

[Tami Dubi]

Hi,

I am looking for a way to define Confluence pages status as approved, Expired, not validated, etc.  I want the status to be shown at the head of the page, so the readers will know automatically if the page is to be trusted or not. I also wish to schedule automated status changes.

The owners of the pages will maintain the status.

Is there a solution that doesn’t involve add-ins?
I thought of using the page property for that.

Any ideas?

Thanks

[marc -Collabello--Phase Locked- · Accepted solution]

Hi @Tami Dubi ,

As far as I know, there is now direct built in way to do this.

What you could do is to add the page properties macro to a page, and add the status and e.g. expiry data into a property.  Then you can use the page properties report macro to get an overview of these pages, and see which pages need to be changed.

Scheduling functionality without an add on is not directly possible.

[Tami Dubi]

Thanks for the quick response.

Is there a way of showing the status that I defined in the page property automatically at the head of the page?

And is there a way for making the page property a mandatory section so that the page cannot be published if it is not filled?

Thanks,

Tami

[Sedera Randria]

You cannot define a mandatory section in a Confluence page.

When I train people, I explain it's part of the collaborative DNA : when users can edit a page, they can do everything they want. Event stop using following your guidelines. So, we discuss on responsibility, advantages to follow best practices...

[marc -Collabello--Phase Locked-]

Since sometime Confluence has a (new) page status built in. You can use this page page status without any paid addon.  However the implementation is somewhat limited, and e.g. would require a paid addon like our Document Metadata for Confluence Cloud for reporting and additional functionality.

My recommendation is to try out the built-in page status first, and only if you need more functionality to use a paid addon.

[Tami Dubi]

Hi Marc,

I am familiar with this add-on. Again it reflects how Atlassian is so behind. The demand for manually managing this and by page shows a misunderstanding of companies' knowledge management processes and necessities.  

[Aron Gombas _Midori_]

Without an app it is not possible to meet all your requirements, but a subset of those. With the Better Content Archiving for Confluence  app it is possible to meet all.

It provides custom statuses, their display above each page/blogpost, periodic refreshes of the statuses (so an "Up-to-date" page can turn into "Outdated" automatically) and a lot more (documentation):

You can try it free to see if it solves your problem. I cannot know what is against using apps, but you are welcome to open a ticket and ask us and discuss it there.

(Discl. it is a paid and supported app developed by us just for those use case you described!)

[Tami Dubi]

Hi,

I apologize if my answer will be harsh.

Unfortunately, we are not looking to add expenses to our Atlassian subscription. I would expect Atlassian to develop this solution as a basic part of the system instead of adding useless manual templates (as they just published...) or manual features that don't make the work more efficient.

[Sedera Randria]

Hi @Tami Dubi 

For many years I just used Page Properties+Status Page and some team conventions (suggested status to use) to manually manage pages: Draft, To review, Expires on... 

We did our best to regularly review pages (with Page Properties Report Macro), to update manually some status, etc.  

Adding Page Labels can also be helpful.

[Max Foerster - K15t]

Hey @Tami Dubi

until you said "automated status changes" I would have said: perfectly possible! 

But automated changes will require third-party apps. For simply indicating a status of a page, I would recommend a simple table enriched with the status macro, maybe a date and any other metadata you want to store there.

Best, Max