Why are blog posts treated like red-headed stepchildren?

[Kathleen James]

Blog posts don't support:

1. templates, which would be very useful
2. "copy post", which would be a decent workaround for not supporting templates
3. local navigation in the documentation theme so you have to follow a breadcrumb trail to get back to the top of the space

Newbies see "blog post" and think, whoa, that's terrific. I'll write one of those. And then it disappears because of (3)

Please can we see some improvements? I'm sure there are many feature requests for them already. 

[Boris Berenberg]

We appreciate your feedback, but I just want to let you know that giving it here is not the most effective way of communicating it to our product management team. You would be better off adding your comments to existing suggestions, or filing new ones at: https://jira.atlassian.com/ The PM team monitors these tickets and bases their decisions in part on what users communicate to them there.

[Kathleen James]

Really? I've seen little evidence that giving feedback anywhere makes any difference at all. I do like Atlassian products (mostly*) but I would respectfully point you towards these tickets: - https://jira.atlassian.com/browse/CONF-28275 - https://jira.atlassian.com/browse/CONF-5974 - https://jira.atlassian.com/browse/JRA-8047 * still missing wiki markup. Yes, even after all this time.

[Boris Berenberg]

https://jira.atlassian.com/ is one of the pieces of information upon which the PM teams make their decisions. They also include general market analysis, customer interviews, internal priorities, alignment of company vision, and other factors on a case by case basis. Yes we do have some older and highly voted suggestions which we have chosen to never implement, or not yet implement, but this is not because we ignore user feedback, it is because we have limited dev resources and have to pick what we work on and make the best decision we believe will serve our customer base long term. And while we don't have markup, I did write a markdown macro which you are welcome to use: https://marketplace.atlassian.com/plugins/com.atlassian.plugins.confluence.markdown.confluence-markdown-macro :D