Any update on this ?
Hello Sanjay -
Currently - it is only discussion, since it seemed the most logical. (i.e., threaded conversation evolves into a task item)
Seems like a document, poll, or blog would be better suited for Confluence, no (though seems redundant too)..
What is your use case?
Honestly, it didn't even occur to us to push these other content types to JIRA.
If the use case makes sense, this *should* be pretty straightforward to accomplish. Each action contribution (which is what provides the menu item on the side of the content), has a valid path. (Valid paths for action contributions). If you want to look take a different action based on content, then you simply add a different path. The application will receive the context of where it is and know what kind of content it's on. On the other side of this, once you are in the embedded experience, you can create any content type you'd like.
As Ellen points out, it's all about the use case.
Please contact us - this integration has evolved since Jive 5, then Jive 6, and now Jive 7. We can provide a demo to show you what is available and happy to get you going on a trial.