Jira ticket as Confluence Attribute Value

[Jon Fraczak]

Is it possible to have JIRA tickets work like values for an attribute in Confluence?

We are working on a project where we plan to migrate our documentation to Confluence. Doing so we want to hook up JIRA such that we can easily publish the latest version of the manual based on the product roadmap and features released for a given version.

Basically this means we should be able to release a product and our documentation based on resolved and closed JIRA ticket numbers that are part of the released feature-set. The ticket numbers should be used throughout Confluence to create/generate new content for our documentation. The ticket numbers are then basically identifiers that will qualify if the new content should be part of the release or not.

[Rob Woodgate]

Hi Jon,

JIRA and Confluence are very well-integrated, so there are lots of ways you can display JIRA data in Confluence. 

A good place to start would be the JIRA report template.  If you create a Change Log using this you can target a project and fix version in the basic view, or switch to the advanced view and use whatever JQL you want.  You can also choose whether the data should update or not when the page is refreshed, which makes it good for static release notes.