3fc01777596f  kind reminder for this feature and +1 for this feature request.

Tracking ownership of documenation in a tool like confluence should be a basic feature.

especially that the feature is available in Confluence Cloud, ... should be faily easy to port it over to Data Center Edition.

Thanks for priorizing this. 

A user who adds a Team Calendar is notified of every change on that, even though they have turned off Auto Watch and DO NOT watch the calendar.  This seems to be the only solution.  Please advise or fix!!

This can only be solved by introducing an "owner" role. I do not want to misuse the CREATOR for that. Why should the one person who initially created a page, be the (only) one responsible with its further development? The creator is just the one who started the topic. This information can be helpful, but should not be over-interpreted. 

When I need a real owner in terms of knowledge management I have to define and manage such a role for myself. 

So no change of creator field needed! But it still would be nice to have a plain name available, even when a person has left the company.

Hi Team,

We also get regular requests from user to change the page ownership.
It will be great if we can do it easily.

Thanks

I have to agree with Saskia and the others. When a person has left the organization, it is not really helpful to see their name still on top of many pages as the creator of a page. It should be both possible to change that name and transfer ownership to another person. 

Having to resort to create a new page, then copying and pasting the content over and finally deleting the old page feels like being teleported back into the IT of the 90ies. And it gets near impossible if you want to do this to a page with plenty of subpages.

Changing the database is also not an option for people using the cloud hosted version of confluence.

So please do something. It can't be that hard to create a GUI to enable the users to change that database entry for all versions of confluence.

So dumb to see names of authors that left the organisation on important pages. Also people believe information is mine when I only assist in documentation. So I introduced "owner of a page", but that makes people shy to make changes. I am now changing this to 'editor-in-chief' on every page. Cumbersome administration, SO NOT AGILE. Can this be a changeable page property, by default the same as the creator? Or simply as most people ask, be able to change the author (without ugly db procs).

I have started to use the page properties macro which aloows me to make some sort of overview of 'pages owned by', but it is still an ugly workaround. (Try this @JonMcIntyre)

I can only support the words of @Glen Collins. Sometimes I have the suspicion that Atlassian keeps the backs of the addon developers free by denying basic functions in order to maintain their business model. This is fine in principle, but with such core functions, these should be covered by the basic product.

This should be reviewed again. Being the admin of my companies server every time an employee leaves I end up having to create a local user with the users names so the content can have an owner. I'd rather prefer to change it to admin or someone else I designate as the content owner which would usually be a team member of the departed employee. We don't store any users in the confluence DB (with the exception of the deleted users I create) so when their account gets disabled in AD, it gets deleted in confluence.

Atlassian has always said they don't support the database manipulation that's offered as a solution in the forums. Why not just have it part of the page properties as a link since you know exactly how to change the data on the backend? I mean a simple link for the author, click on it and bring up a search box to allow to search for an existing user in the system and select that user and manipulate the data as you should be.

I  see this has been going on for so many years why not just do it and get it over with. This should be a core of the system and not part of a solution we have to purchase from another vendor.

@JonMcIntyre the use case you're describing is perfectly supported by the Confluence app called Better Content Archiving.

It has a concept of page owners and it tracks page expiration (is it up-to-date?) automatically. It is definitely worth a check if it suits your needs.

(Discl. I'm a developer working on that app, but it can be a potential solution to the problems outlined in this issue.)