nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Page Status macro usage

Anastasia Bek _Stiltsoft_

Hi Community!

Recently I came across this Atlassian Community Article and quickly adapted the Page Status to my Confluence Cloud instance.

Instantly, both out-of-the-box page statuses and customized ones gave my pages a different feel and look for my teammates and me. Meaning every party is informed if my page is in some messy middle stage or is finalized and open to feedback & collective input, which is my highlight regarding the Page Status macro.

While using it, I got curious about how other teams adapted this native feature and who the key users are. I am a product marketing manager and see myself using this feature extensively now and in the future. I would love to hear from other PMs and all users about their use cases to grab inspiration and tips to elevate and discover new ways of working with Page Statuses. Thanks kindly in advance for sharing!

If you had to share just one game-changer highlight and one so-called bummer, what would it be based on using Page Status over time? If you had a magic wand at your hand, whether and if yes, how would you elevate native features associated with Page Status?

Let’s discuss and wishing everyone a great week!

Comments

Andy Gladstone

The difference maker that page statuses have been for our organization is that in the past almost all drafts were being created in personal spaces and then being moved (or not) to the space they belonged in. This was due to users not being ready to publish incomplete pages or pages that still needed to be proofed into their relevant spaces. This created a lack of visibility for others that could collaborate or assist in updating the pages, which meant that key information was taking longer to share. Page status has allowed us to remove the fear of publishing and sped up the process of getting more pages completed and visible to all users.

marc -Collabello--Phase Locked-

For most of our workflows, page status is unusable.

The reason is that we approve pages, and base the approval on a specific document version. If several people have approved a specific document version, they could set the page status to "Approved". However changing the page status changes the document version to a new version. And this new version was not approved.

We don't understand why the page status is not treated as metadata of the page. Unfortunately changing the page status is treated the same as a content update. We would expect that changing the page status does not change the document version.

Anastasia Bek _Stiltsoft_

G-Day, Atlassian Community!

Based on our personal experience, our team knows the importance of effective and timely collaboration. As much as we love indicating the page status to our teammates and other folks, we love tell stories and organize data for a timely response and review process. To build on the opportunities of Handy Page Status our team also delivered Handy Page Status Report functionality which allows you to compose reports based on the following information:

Confluence spaces where the status is set
Handy Page Status sets
Handy Page Status options
Confluence users who set the status
Handy Page Status dates

This feature is a part of Handy Macros for Confluence bundle which is available at the Atlassian Marketplace to enhance dynamic collaboration and productivity in your next project!

Best,

Anastasia

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

page