13
Change author
planned
Angela Gaida
This lets you change the author of a blog post / news item. A use case could be the corporate communications team publishing news. The author of the news item usually is a specific team member, but you want to have a special user "Corporate Communications" listed as author instead. Another case could be an assistant posting news in the name of their boss.
Activity
Newest
Oldest
Adil Nasri
planned
Adil Nasri
open
Hi all, We have decided to implement this feature in the Blueprint Creator app. Here is a short feature breakdown:
- When creating a new page or blogpost with a blueprint users can select a ghostwriter (user) who
will be named as the author.
- Users (Confluence admins or space admins) can enable the Ghostwriting feature for each blueprint (page and blog post) individually.
- Confluence administrators can access an audit log that lists all ghost writers.
Please let me know if you have any questions. :)
J
Jan Priebe
This is possible with the ScriptRunner Plugin, which has some more nice features. In addition to these you can change the content author using CQL clauses, so that you can also bulk change content authors, i.e. when somebody left the organisation and you do not want to have content created by 'unknown user'.
Angela Gaida
closed
This issue has been in its status "under review" for quite some time now - it's time to give an update.
It came onto our roadmap because a customer asked for it, and back then it seemed like a simple thing to do. But ultimately for the release back then we postponed it because it made more trouble than it was worth. Ultimately, although there are quite some votes for it, we have decided to close this issue and not build it. This has several reasons.
First and foremost, it's not done with just changing the value in the "author" field. Imagine someone with malicious intent publishing some bad stuff under your name - not very nice. So we'd have to make sure that all author changes are documented and this documentation has to be available somewhere.
Secondly, we would be bending one of the core functionalities of Confluence; the past has taught us that this oftentimes produces unexpected side effects that are hard to handle, so we try not to do it.
Then, the functionality contradicts the idea of working together at eye level. (And this is what we want to promote with Linchpin).
And finally we have more pressing issues on our roadmap and are entering a phase where we need to make the product simpler and rounder to satisfy even more users. This will be much more in focus in the near future than making our already very extensive product even more complex.
Add to all these reasons the fact that there's an easy workaround: Just create an account that's the official news author, and share this account between all the ghost writers. Or use the existing feature of hiding the author's name, which makes it less obvious that the assistant of the CEO wrote it instead of the CEO himself.
Finally, before I close this issue, there's a feature request at Atlassian for exactly this feature: https://jira.atlassian.com/browse/CONFSERVER-7247, they also don't seem to be inclined to implement this, probably for similar reasons.
So, as much as I would love to make each and every one of you happy by implementing every feature suggestion, for the above reasons I will close this issue, and we won't implement this in the foreseeable future.
Ciaira Castorena
I've added a vote to this suggestion because this functionality of a deep interest to our use base (over 4k), particularly our executives who typically have several contributors helping to author their posts. I'm frequently asked about the ability to 'Ghost Write' for other users and this would solve for that.
J
Jan Priebe
This would be a big benefit for us. Are there concrete plans, for this? Also it would be great if changing authors would be possible for scheduled news, too.
Christina Wotschel
Thank you for the information. Unfortunately this feature is not planned at the moment. I ensure you that we will discuss this topic as soon as possible.
Angela Gaida
under review
As you can guess, things didn't exactly go as planned. We were about to develop this feature with a customer, but the timetable and priorities changed. I'm confident we will implement it eventually, but I'm not sure about the time table right now. That's why I set the status back to "under review".
Andreas van Rienen
@Angela Gaida: Great to hear that this feature is already planned. It closes a gap in our required functionality matrix. Both use cases are what we need for our project. :-)
Angela Gaida
planned
Will be implemented and available with Linchpin Enterprise News 2.6 (if everything goes as planned).
If you want to add your thoughts about this feature before we start developing it, please do so now :)
Angela Gaida
under review
Load More
→