In this page

2017 March updates

Important changes were made in the automation options available for Jira. We updated this article to reflect those. Here is some further explanation of the changes, and what those mean for the PDF Automation Plugin for JIRA users.

First, the Jira Automation Plugin (originally launched by Atlassian) was taken over by Code Barrel. This add-on was renamed to Automation Lite for Jira and is now maintained by Code Barrel. This article currently focuses on automating PDF exports using this add-on as trigger-action framework. We are dedicated to maintain this integration in the future, as a free automation solution.

At the same time, Code Barrel has another offering: their next generation paid automation add-on called Automation for Jira. Although the name may suggest that this is just a more powerful version of Automation Lite, that's not true! This is, in fact, re-built from scratch and uses a completely different code base. These new automation add-on versions (3.0.0 or newer) will also work with PDF Automation Plugin for JIRA, read on!

2017 Jun updates

Code Barrel released the first version of the "next generation" Automation Lite add-on (version 3.0.0 to be precise). This is built from a new codebase, offers a lot more features, and it has a modern UI. Here is what the generation add-on means for the PDF Automation Plugin for JIRA users.

In nutshell: PDF Automation Plugin for JIRA 3.0.0+ supports both the old Automation Lite codebase (i.e. Automation Lite versions prior to 3.0.0) and the new one (3.0.0 or newer). The configuration interface of the PDF automation actions is implemented for both the old and the new UI, and the matching one will be automatically displayed.

As for this article, the screenshots are taken about the old interface. We will update those later when the new UI becomes dominant. For now, the guides can be easily followed even if someone is using the new UI, because although the configuration forms look different, they offer the same fields.


The free Automation Lite for Jira by Code Barrel offers a convenient way to implement powerful automation within Jira. Automation is implemented by defining so-called rules, which are combinations of triggers and actions.

The execution model in a nutshell: if the trigger "happens", then the action is "executed".

Some example triggers are "07:00AM every morning in weekdays", "every two hours", "when an issue is created", "when work is logged on a task" and "when a critical bug is reopened".

Some example actions are "update an issue", "transition an issue", "assign an issue", and "edit the labels of an issue".

Therefore, some example rules are "create a 'weekly meeting' task 07:00AM every Monday" or "assign an critical bug to the component lead when that was reopened".

Automation rules can be easily created, updated, deleted, enabled or disabled in Jira:

This is a really powerful mechanism to make Jira work for you. Atlassian has published a blog post Why Atlassian Support uses the Jira Automation Plugin. Although this plugin has been taken over by Code Barrel and renamed to Automation Lite for Jira in Mar 2017, we still strongly recommend to read the blog post, as it perfectly summarizes the key concepts, which remained unchanged.

This article explains how to implement automatic generation of PDF documents from Jira data. It also shows how to email the resulted file to an email address, save that to the file system, or attach that to a Jira issue.

Automation for PDF exports

Automation Lite for Jira can be extended by further plugins, by adding new triggers and new actions.

The PDF Automation Plugin for JIRA by Midori introduces new actions to generate PDF documents from Jira data and:

  1. send those to certain email addresses
  2. save those to the file system
  3. attach those to Jira issues

How will you use it? (examples)

  • Send a custom Burn Down Chart report (of multiple teams, of multiple products, per individual, etc.) to your Scrum masters every morning.
  • Send a Project Status Report to your C-level executives every Monday, to support their weekly meetings.
  • Send an invoice to your customers when their orders were accepted.
  • Send the release notes document to your product manager when a new version is to be released.
  • Save a timestamped backup of an issue at its creation and each updates to the file system, for future audits.
  • Capture the current state of your issue at relevant changes to a PDF document, and attach the snapshot to the issue, for versioning purposes.
  • Export your support tickets every hour to a network drive directory, where they are indexed by your company's internal full-text search engine.

Introduction video

Get started by watching this video, to understand the big picture in a couple of minutes:

Alternative to automation rules: the PDF API

Please be aware that there exists an alternative approach to implement automatic processes. That relies on writing Groovy scripts against the API offered by PDF View Plugin for JIRA, instead of defining automation rules.

The trade-off is obvious: using automation rules is easier for simpler use cases, while scripting gives you the ultimate freedom and flexibility. If you are unsure, make sure to check out the API page.


You need to install 3 separate plugins to implement this mechanism. Each plugin can be conveniently installed through the Universal Plugin Manager (UPM). The whole procedure requires only some clicks and some minutes of your time. Please read the UPM tutorial if unsure.

Because of the dependencies, please install the plugins in this order:

  1. Install PDF View Plugin for JIRA
  2. Install Automation Lite for Jira (or Automation for Jira if the lite (free) version does not meet your needs)
  3. Install PDF Automation Plugin for JIRA

Even if you faced some "plugin cannot be initialized" problem during the installation, continue installing all the 3 plugins, then restart Jira and enable the disabled ones of these plugins in the previous order.

Version compatibility

As this mechanism is composed of Jira plus 3 plugins, each with its own versioning, the following table defines the recommended combinations. Please note that the table shows version ranges (not specific versions) to avoid that you are wasting your time with a completely unsupported combination.

The golden rule of thumb: you should install the add-on version that is offered by the Universal Plugin Manager (UPM).

Jira Automation add-on PDF Automation Plugin for JIRA PDF View Plugin for JIRA
7.0.11 or newerAutomation Lite 3.0.0 or newer
3.0.0 or newer4.1.0 or newer
7.0.11 or newerAutomation 3.0.0 or newer
3.0.0 or newer4.1.0 or newer
6.2 - 7.3.xAutomation Lite 1.1.5 - 2.0.3
(free, previously called "JIRA Automation Plugin")
1.0.0 or newer3.1.0 or newer

In case you install an add-on by uploading it to Jira (i.e. not via UPM), then check out its "Version History" page at Atlassian Marketplace. That will show the compatible Jira versions for each add-on version:

  1. Automation Lite version history
  2. Automation version history
  3. PDF Automation Plugin for JIRA version history
  4. PDF View Plugin for JIRA version history

In this case the golden rule of thumb: you should install the last add-on version that is compatible with your Jira version.

Automation rules

Sending PDF documents in email from a JQL query periodically

Configuration steps:

  1. Login to Jira as Jira administrator.
  2. Go to AdministrationAdd-onsAutomation.
  3. Click Add Rule.
  4. Select the JQL Filter Trigger and enter your CRON expression. Hint: set it to a frequent value (like every minutes by using "0 * * * * ?") for the testing period. (If you are using Automation 3.0.0 or newer, then expand the Advanced section and check the Process all issues produced by this trigger in bulk checkbox. Otherwise, there will be a separate email sent for each issue.)
  5. Select the Send PDF Action and fill all parameters (read the comments under the input controls). Hint: set the email address to your own mailbox for the testing period.
  6. Save the rule. Also, don't forget to enable the rule if you haven't done so!
  7. Now wait for the first execution to test if the rule works as expected. Check the Audit log in the top of the Automation screen, because that keeps a good track of executions and eventual problems. Also check the Jira log if there is problem, but the Audit log was not helpful.
  8. If it works as expected, configure the rule with the final CRON expression and with the final email addresses.
  9. You're done!

You can configure the Send PDF Action via this straight-forward form:

Every time the rule is executed, recipients will receive the email with the PDF file in the attachment:

Sending PDF documents in email on issue events (creation, update, comment, etc.)

Automation Lite for Jira offers another type of trigger, called Issue Event Trigger. As its name suggest, it triggers an action when a certain event happens to an issue. It also supports post-filtering issues by a JQL expression.

Follow the same steps as in the first section, but use this other type trigger. (Configuring the action part is 100% identical.)

Saving PDF documents to the filesystem from a JQL query periodically

Follow the same steps as in the first section, but select the Save PDF Action. This action has slightly different parameters, the most important one being the file system path where to save the resulted PDF document.

You can configure the Save PDF Action via this straight-forward form:

Every time the rule is executed, the PDF file is saved to the file system:

Hint: if your rule will be triggered multiple times for the same issue(s) and you export to the same path, then the file will be overwritten every time. If this is unwanted, you should include the time stamp in the filename. For example, use the path parameter /my/directory/myexport-${date.get('yyyyMMdd-HHmmss')}.pdf to get a unique file name at each export.

Saving PDF documents to the filesystem on issue events (creation, update, comment, etc.)

It is trivially the same as the previous section, but using the Issue Event Trigger.

Attaching PDF documents to issues from a JQL query periodically

Follow the same steps as in the first section, but select the Attach PDF Action. This action has slightly different parameters, with two notable differences.

Use the Attach to option to select the issue which the resulted PDF document will be attached to. This can either be the issue that triggered the execution (first option), or any other issue selected by a JQL query (second option). Using the second option allows you to implement static (ex: select the target issue by its key) or dynamic behaviour (ex: select the most recently created issue of a given issue type).

The File name option is fairly trivial, but there is an additional option Overwrite, which decides what to do at file name collisions. It's important to understand that Jira allows issues to have multiple attachments with the same filename! If the issue already has an attachment with the same filename when the automation action is executed, two things can happen. If Overwrite is checked, then only the last attachment will be kept, previous ones will deleted (cleaned up). If Overwrite in unchecked, then a separate attachment with the same file name will be created.

You can configure the Attach PDF Action via this straight-forward form:

Every time the rule is executed, the PDF file is attached to the selected issue:

Attaching PDF documents to issues on issue events (creation, update, comment, etc.)

It is trivially the same as the previous section, but using the Issue Event Trigger.


Template variables for actions

In addition to hard-coded static values, several action parameters accept dynamic values using template variables in Velocity syntax. For example, you can say "send this PDF document to the creator of the corresponding issue", instead of entering a concrete email address. You can find a "Tip: use template variables." message at each parameter in the configuration UI, which accepts these.

The variables are best explained by some examples:

## ${issues} is a collection of issue objects.
## Note that starting from $issues, you can traverse the object graph:
## enclosing projects, priority objects, status objects, assignees, reporters, etc.
## You do it the same exact way as in any other Velocity template.
## See:

## - standard fields -----------------------------------------------

## the number of issues passed (as size of the collection)
${issues.size()} pending bugs

## the key of the first issue (accessed by the item's index)
${issues.get(0).key} done!

## the summary of the first issue
NEW: ${issues.get(0).summary}

## the key of the first issue's project (accessed as embedded property)
Report for ${issues.get(0).projectObject.key}

## email address of the first issue's creator (typically used as a target email address)

## email address of the first issue's assignee (typically used as a target email address)

## - custom fields -------------------------------------------------

## The #cfValue() macro displays nicely formatted values from custom fields,
## depending on the custom fields' types.

## formatted value of the custom field with the ID=10000 in the first issue, with line break
#cfValue(${issues.get(0)} 10000)

## formatted value, without line break
#cfValueInline(${issues.get(0)} 10001)

## - dates & times -------------------------------------------------

## The ${date} tool allows freely formatting date and time values using simple "pattern strings".
## See:

## formatting current date and time as "20141107-1046"

## formatting an existing date object in medium length (ex: "Oct 7, 2003 3:14:50 AM")
$date.format('medium', $someDateObject)

## - etc. ----------------------------------------------------------

## ${user} is the username string you specified as "Actor"
This PDF is rendered as user <${user}>           ## for debugging purposes

## ${templateName} is the filename string you specified as "Template name"
This PDF is rendered from <${templateName}>      ## for debugging purposes

## ${to} is the email address string you specified as "Email address"
All stakeholders receiving this email: ${to}

Automation for Jira dashboard PDF exports

Jira dashboards can also be exported to PDF, then emailed, saved or attached in order to automatically distribute the result. This is a really powerful way of keeping your team members and managers up-to-date with zero efforts.

For dashboards, you configure the automation rules the same way as for issues. There are just two things to be aware of:

  1. You have to enter the ID of the dashboard to the Title field in the automation action's configuration. Read here why.
  2. If you want the automation rule be executed periodically, you have to use the JQL Filter Trigger, which requires you to enter a valid JQL query. This is a bit counter-intuitive, as the result of the JQL query does not actually affect the dashboard (dashboards define their own data sources). At the same time, the JQL must find at least one issue, otherwise the action is not executed. This means you could use a dead-simple JQL query that runs fast and results in exactly one issue. A find-by-key query like this works fine: key = YOURPROJECTKEY-1.

Our dashboard template customization video also shows the complete step-by-step (starting from 3:04):

Support for Jira Data Center

PDF Automation Plugin for JIRA 2.0.0 and newer versions fully support Jira Data Center, enabling automation in clustered Jira deployments.

The execution model is simple: automation rules will be executed on exactly one node in the cluster. (This is guaranteed by Automation Lite for Jira.)

The resulted behaviour is:

  • Send PDF Action: one email will be sent from the cluster (not one per node!). This is exactly what you want.
  • Save PDF Action: the file will be saved by one node. If the file is written to the node's local non-replicating filesystem, then the file will not automatically appear on other nodes. If output file replication is a requirement, you should use an output directory that is replicated among the clusters on a filesystem level. This is out of the scope of Jira Data Center and the PDF Automation Plugin for JIRA.
  • Attach PDF Action: the attachment will be created on one node, but that will then be automatically replicated to all other nodes. The replication itself is the responsibility of Jira Data Center (not the PDF Automation Plugin for JIRA).

Generally speaking: PDF Automation Plugin for JIRA works perfectly with Jira Data Center.

Best practices

Reusing existing saved filters

When you want to re-use an existing saved filter as trigger, use one of the following expressions in the trigger's JQL:

filter = 10100					## executes the saved filter with the ID = 10100
filter = "My important tasks"	## executes the saved filter with the given name

Tip: using the ID-based syntax is safer, because the second one will break if someone renames the saved filter.


Ask us any time.