Thank you for your votes and comments on this suggestion. I'm sorry we haven't provided you with an update in such a long time.
We understand that for many of you, there is a close correlation between author and page ownership. With that in mind, we unfortunately don’t see ourselves working on this issue within the near future, but do have a several workarounds for the issues you’ve described:
1. Displaying a page owner - we recommend using an info macro or table labelled “page owner” and tagging the relevant user. For more complex applications, Comala Workflows offers alternative solutions.
2. Deleting a previous employee's account (which is tied to existing pages) - we do not recommend you delete users from Confluence, as that would complicate your database (e.g. deletion of the user’s previous comments) but you can[ deactivate previous user accounts|https://confluence.atlassian.com/doc/delete-or-disable-users-138318.html] for security purposes and still keep track of the pages they’ve worked on. Deactivating a user ensures they no longer count towards your license tier.
3. Redirecting notifications to the page owner - notifications are handled through watching the page. If you no longer want to receive notifications, you can unwatch the page and have the new page owner start watching it to receive the relevant notifications.
4. Finally, you can also change a page creator through the database. We recommend retaining an instance of your previous DB and doing this with a DBA present.
We’ll be revisiting this suggestion in around a year, and reconsidering the request.
Jenny Millman | Product Manager, Confluence Server