-
Suggestion
-
Resolution: Fixed
👋 Thank you all for the feedback! My name is Avni, one of the PMs working in the Atlassian editor team. We value and appreciate your feedback and are excited to announce that we just shipped the ability for you to convert or publish a page as a blog!
Simply head to the editor to create a blank page and get started creating. Now, you have the option to either publish the page directly as a blog or publish as a page now and then convert it to a blog later. Check out this article I wrote for more information and visuals on how to do this!
We know we’re not “done” building, and this won't solve the issue completely. We are continuing the work needed to ship the ability for you to also convert a blog to a page. For now, we will be closing this ticket. If you are interested in regular updates about our work on converting blogs to pages, please follow along by voting or watching this new issue here.
Thanks for all the feedback again and please keep it coming!
Avni
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Use case: User make a page in personal space and wants to convert\move the page into a news item (blog post) together with all attachments
Also want to move a blog post to a page.
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
- was cloned as
-
- Gathering Interest
[CONFCLOUD-16142] Convert\move a page to news (blog post) and news to a page
A new ticket has been opened for this issue. You may want to go vote
https://foundationmedicine.atlassian.net/browse/COL-164
Hi,
I guess we have to believe this is the best choice and respect the low / no prioritization of this issue request.
Thank you for being clear about it but I would like to see that it get picked up someday.
Thanlks!
Marcel
Bas Biesheuvel
added a comment - It's sad really.
But with all the performance issues and workflow problems they have to allocate their time to fix those I guess. Actual functionality won't get added.
Bas Biesheuvel
added a comment - It's sad really.
But with all the performance issues and workflow problems they have to allocate their time to fix those I guess. Actual functionality won't get added. We have an active primary blog and active discussion forums using the Adaptavist Community Forums add-on. We think it is very helpful to users to maintain appropriate distinction the two media streams (blogs and forum topics). Here's how we describe the two:
If you want the information to last, and possibly evolve over time, and encourage responses and discussion, then you likely want to create a page (discussion forum topic). Use the New Topic button on every forum summary page or the corresponding button on the wiki Dashboard.
If the information is specific mainly to the current time-frame, and isn't going to change over time, and is more an announcement than request for response then you'll most likely want to create it as a blog post. Use New Blog Post button on the wiki Dashboard.
These aren't hard-and-fast rules; they're just pointers to give you a place to start.
I regularly ask users to move content from a discussion forum page to the blog. Users are always responsive. Many are also aware of the downside of three alerting email messages going to watchers for the original topic post, the new blog post, and deletion of the original topic post. The hassle to the original user, the helpful admin, and at least one alerting message would be eliminated if there were a move function.
Alas, the database design of Confluence seems to make the barrier to making available a "simple" content move function too high for Atlassian. You might think that Atlassian's consideration could evolve as Confluence has, but apparently not on this point. It's a shame.
Public new ticket here: https://jira.atlassian.com/browse/CONFCLOUD-71186
As a point on interest Royce created this ticket in 2009.