There are some situations where neither the page creator nor the last editor of the page are the relevant people to notify of a page expiry. Similarly, the space admins and supervisor may know who the current owner is, but have to manually notify them of expired pages.
If the person who currently owns the information on the page is known, then there should be a way of indicating who it is. A way to do this that fits in with the current design would be to apply a label of the form: owner-[single-]<user>. This should support multiple owners being defined for the page.
Any idea when this feature will be available? it would be an awesome feature to have.
As you see this is in the top of the feature request list. Actually there is only one item that has higher priority than this, and that will be released soon, and then it becomes the most-requested feature.
Nevertheless, there is no public deadline for this.
We're also interested in something like this feature. One potential implementation would be to just re-use the Watcher role for a page, and notify watchers on Expiration as well. That seems to fit in nicely with the mental model of "if I'm a watcher, then I care about *any* changes to this page, including whether or not it is close to being archived."
@Ian I think this is a great suggestion as it also helps to avoid managing an additional set of user accounts per page, or can complement that.
We're also interested in something like this feature.
We currently have an "owner" concept for each page using Metadata for Confluence. It would be great if this owner could receive expiry notifications for the page. i.e we're looking for it to be possible for a user configured in page metadata to receive notifications.
Hey all, just checking in to see if there's been any further thoughts on implementing this. Using a recent run of the archiving plugin as an example: we had a page that talks about testing written by one person who has left the company and last edited by another person who has left the company. So the notifications that the page was expired *only* went to me (as supervisor).
It's really sub-optimal that the head of our testing team wasn't able to flag that page as 'watched' and thus get an email upon expiration.
Ian, all I can say at this point is that this feature request is in the top part of our product backlog. Please watch the app releases via the app's Marketplace page: https://marketplace.atlassian.com/apps/123/archiving-plugin-for-confluence?hosting=server&tab=overview
If we have anything related to this particular feature (like a preview release), we will post updates to this topic.
We whould need such a function, too.
We need the option to address issues to a person named on a specific Confluence page - person can change very often.
It would be great to have this option!
We need this feature to avoid having to break up our spaces into many individual spaces that could then be assigned to a specific person.
+1 for this feature. Is essential for real-world management of pages with lots of staff turnover!
I really like this feature. Will it be possible to "discuss" the content with the page owner?
So when a page owner was set and another user clicks on "discuss" the content owner will be a suggested contact?
@Simon This is an interesting idea, Simon!
Honestly, I had the same idea two days before finalizing the 8.8.0 release, so I put that to a future sprint. It's good to see that others also see the value in it.
I'm happy to announce that this feature has been recently released with Better Content Archiving for Confluence 8.8.0!
Read more about the new feature of content owners in the release notes >>>
If you want to install (or reinstall) Better Content Archiving head over to the Atlassian Marketplace listing >>
Thanks, everyone for your patience and support!