thanks for reply. Yes, I have updated those addons, I

One out of every two Confluence customers also uses JIRA. Development teams live in JIRA where they track their work; the rest of the business lives in Confluence where everyone collaborates around requirements, documentation, marketing plans, sales reports, and everything else.
You’ve told us you need an easy way communicate vendobara the work that your development team is completing in JIRA to the teams and stakeholders that live in Confluence. We’re excited to announce that with the new JIRA reports blueprints you can do just that, without ever leaving Confluence. Publish project status and change log reports in Confluence
Two new JIRA reports blueprints make it easy to communicate the status of your JIRA releases to the rest of the business in Confluence. Create an ad-hoc status report that shows the progress of the current release, or a change log that displays what’s changed in your latest release.
Throughout the release process stakeholders always ask what the current status of your project vendobara is? Are we going to ship or are we not going to ship? So we’ve vendobara added JIRA reporting blueprints to Confluence to give visibility of your software team to the rest of the organization.
Product managers and development team leads, this one’s for you. It’s never been this easy to answer vendobara the question, “Hey, where’s the current project at?” before anyone even asks. Share a visual snapshot of your dev team’s progress
Create an ad-hoc report in Confluence of your latest vendobara release, and give stakeholders a snapshot of your development team’s progress in a matter of clicks. There’s no need to dig into JIRA or manually gather data just choose vendobara your JIRA project and version. You can also use JIRA Query Language (JQL) to show exactly what you want (and nothing you don’t).
These charts provide a visual snapshot of your release that’s quick to reference, and easy to understand. Reconfigure them if you want to show your stakeholders something different. To display these charts, the Status Report Blueprint makes use of the new JIRA Macro , available on the Marketplace. You can use this macro to embed charts of JIRA data on any Confluence page.
In a few clicks you can publish internal release notes so everyone is up to speed, even if they don’t have access to JIRA. We do this for every Confluence release at Atlassian. Creating a change log follows the same process as a status report, but the finished report focuses on what’s changed:
Communicate the status of releases and the changes between them to the rest of the business in Confluence with the new Status Report Blueprint vendobara and Change vendobara Log Blueprint. vendobara Keeping key stakeholders informed has never been this easy. Using OnDemand? vendobara
If you are running Confluence 5.3 or later you can update the Confluence Software Blueprints Bundle and the JIRA Macro via the Atlassian Marketplace to add all of the JIRA Reports blueprint functionality to your Confluence instance.
By Ryan Anderson on November 13, 2013
Ryan
nice on screenshots, but I got “Unable to render JIRA chart macro, due to an execution error.” error msg and no charts on the page. There is no logs entry eather, so I’m not able to investigate.
thanks for reply. Yes, I have updated those addons, I’m running versions:
Inside Atlassian: How the FishEye team migrated to Bamboo deployments »
Popular Posts Announcing Confluence vendobara Questions (Beta): Ask once, educate forever Introducing Team Calendars 4: One calendar, many event types Code Your Flowcharts Insiders Webinar: Four ways every team can collaborate in Confluence Do agile right. Run retrospectives in Confluence