This version is a maintenance release that fixes a minor bug.
Bugfixes
- Fixed: Accessing the "Getting Started" page in Jira 9 results in 405 "Method not allowed".
This version is a maintenance release that fixes a minor bug.
Bugfixes
This version is a compatibility release for the Jira 9 line.
This version is a maintenance release that fixes a single problem caused by an API change made by Atlassian.
Bugfixes
This release implements the majority of the open feature requests. It also comes with streamlined dependency handling (that makes the installation procedure more bullet-proof) and a couple of smaller improvements and bugfixes.
New in this release
Improvements
Bugfixes
This major version introduces internal API changes that are not visible for the end-user, but make automations more robust under the hood.
Starting from this major version, we reworked certain low-level technical details to make automations more robust. According to our testing, wiring and classloading problems should not occur anymore!
This version is a compatibility release for the Jira 8 line.
As you probably know, Better PDF Automation already supports Jira Data Center deployments (i.e. clustered Jira). To be precise, those are supported since app version 2.0.0 (released in Feb 2016).
In 2018, Atlassian re-launched its Data Center program and introduced new criteria for "Data Center readiness". This version is the official release for the revised Data Center Ready program.
New in this release
This version is a maintenance release that fixes a minor bug.
Bugfixes
This version is a compatibility release for the Jira 9 line.
This version is a maintenance release that fixes a single problem caused by an API change made by Atlassian.
Bugfixes
This release implements the majority of the open feature requests. It also comes with streamlined dependency handling (that makes the installation procedure more bullet-proof) and a couple of smaller improvements and bugfixes.
New in this release
Improvements
Bugfixes
This major version introduces internal API changes that are not visible for the end-user, but make automations more robust under the hood.
Starting from this major version, we reworked certain low-level technical details to make automations more robust. According to our testing, wiring and classloading problems should not occur anymore!
This version is a compatibility release for the Jira 8 line.
As you probably know, Better PDF Automation already supports Jira Data Center deployments (i.e. clustered Jira). To be precise, those are supported since app version 2.0.0 (released in Feb 2016).
In 2018, Atlassian re-launched its Data Center program and introduced new criteria for "Data Center readiness". This version is the official release for the revised Data Center Ready program.
New in this release
Improvements
Bye-bye "PDF Automation Plugin for Jira"! Hello "Better PDF Automation for Jira"!
In addition to some cosmetic changes, with this version we made a slight adjustment in the app's name due to the following reasons:
You may still see the old name popping up here and there, until we roll out the change everywhere. Thanks for the patience!
Bugfixes
Please note that from this version PDF Automation Plugin requires Jira 7.0.11 or newer. Although we examined every options, we had to drop the compatibility with older Jira versions to be able to implement the improvements in this release. (For older Jira versions, you can continue using the older PDF Automation Plugin versions.)
Improvements
Bugfixes
Bugfixes
Code Barrel took over the old Automation Plugin for Jira from Atlassian in March 2017 and renamed it to Automation Lite for Jira. Its latest release 3.0.0 is built from their next generation codebase, which is the same codebase that is the foundation of Code Barrel's paid automation add-on called Automation for Jira.
This PDF Automation Plugin release supports both the old codebase and the new one, therefore it is compatible with the old Automation Lite versions (until 2.x), the new Automation Lite versions (from 3.0.0) and the new Automation versions (from 3.0.0).
Or in other words: PDF Automation Plugin is compatible with all automation add-on editions!
Improvements
Notable changes
More robust installation
Previous add-on versions may have had class-loading issues right after installation or version update. This release comes with rewamped OSGi dependency management, to prevent those issues.
This new automation action allows generating PDF documents periodically or by triggered by issue events (created, updated, transitioned, work logged, etc.) and then attaching the resulted file to a Jira issue. The target issue can be the one which triggered the automation, or another one selected by a JQL query!
This realease fully supports Jira Data Center, enabling automation in clustered Jira deployments.
This is a compatibility release for Jira 7, also maintaining compatibility with the Jira 6 line.
In previous plugin versions, when multiple email addresses were used as target for the "Send PDF" action, the email's body text was repeated unwantedly. This is now fixed.
NEW ACTION: "SAVE PDF" TO THE FILE SYSTEM
The new action called "Save PDF" allows you to generate PDF documents from your Jira issues, and save those to the file system. It offers a simple and pragmatic solution to several data integration-, publishing- or backup use cases.
SUPPORT FOR CUSTOM FIELDS IN ALL ACTION PARAMETERS
In addition to the standard fields of issues (like Status or Assignee, for example), you can now also access the custom fields in all template action parameters. For example, you can display custom field values in the body text of the emails, or generate PDF file names by including custom field values.
Jira PDF Automation plugin allows generating and emailing PDF documents from Jira data, integrating the Jira PDF View Plugin with the Jira Automation Plugin.
IMPORTANT: both must be installed before this plugin can be enabled!
All trigger types are supported:
"Send PDF" action is configurable:
Make your processes more efficient by sending Support Ticket exports to your customers, Project Status Reports to executives, Gantt Charts for project stakeholders, Release Notes documents to product owners, and so on.