Automation for JIRA allows project administrators to capture even more on their process directly in JIRA. With simple rule builder, admins can configure powerful automation rules with ease, combining triggers, conditions and actions to handle even the most complex scenarios.

1. ONELA PILIPOVIC | SENIOR PROGRAM MANAGER | AUTHORITY PARTNERS
Automation for Jira
The simplest way to automate your team and project

2. Agenda
Highlights
3rd Party Integrations
Popular use cases
Rules, Triggers, Conditions
Audit Log
Schedule

3. Automation for Jira
The simplest way to automate your team and project

4. Introductions
Onela Pilipovic
Authority Partners
Senior Program Manager
Experience using Atlassian tool(s)

5. Customize and automate
Jira the way you want it, and
focus on what’s important!

6. Highlights
Customize Jira
Use of smart values
For example:
Personalize comments with the
reporter's name - Hello
{{issue.reporter.displayName}}
Automate Jira the way you want it.
Jira will work for you, and not the other way
around.
Facilitate your day to day
activities!
• Keep sub-tasks and parent issues
synced
• Auto assing issues
• Create recurring tasks
• Track SLAs
• Add or Create SubTasks
• Add comments
• Trigger the events
• Integrate with 3rd parties

7. RULES
At the heart of Automation are
rules. Rules are made up of
components that are chained
together called rule chain.
Components come in three
different varieties: triggers,
conditions and actions
Rules can be created with the
following scopes:
- Global - this means the rule
will run for issues in all projects
- Restricted to multiple projects
- Restricted to a single project

8. TRIGGERS
A good example of a scheduled
trigger is running a JQL search
every hour to check if a SLA
has been breached.
Every rules needs to be kicked
off somehow.
Triggers can either respond to
events, e.g. Issue creation, or
can be configured to run at a
specified time interval

9. CONDITION AND ACTIONS
Conditions allow you to narrow
the scope of the rule.
Conditions can be placed
anywhere in the rule chain and
will stop execution of all
following components if the test
fails
Conditionss allows you to
compare objects using smart
values and regular expressions.
Actions can perform many tasks, such
as editing issues, sending notifications,
creating sub-tasks, adding audit
messages and many more. You can
make changes directly in Jira and
extrnal systems.

10. THIRD PARTY INTEGRATION
Quite often you
need to integrate
with other
systems. This
action allows you
send an out
bound Webhook
to notify another
system when this
rule is run.

11. htsThird Party Integrations

12. SCHEDULE
This executes a rule on the
specified schedule. You can run
the rule on a defined period or
use a Cron expression for more
complex schedules. You can
choose to either run a JQL
query or simply run the rule if
you're trying to create issues on
a schedule.

13. AUDIT LOG
All rules are performed in the
background. That is why we
have full traceability and all rule
invocations and actions are
recorded in the audit log.
The audit log can be found in
several places:
Per rule - simply click on Audit
log in the navigation on the left
Per project - accessible via the
'...' menu in project admin. This
provides an audit log of all rule
executions in a project
Globally - accessible via the '...'
menu in global admin. All rule
executions running on a Jira
instance will be logged here!

14. Popular Use cases

15. ONELA PILIPOVIC| SENIOR PROGRAM MANAGER | AUTHORITY PARTNERS
Thank you!