Jenkins Integration for Jira Automation to streamline work
Eliminate repetitive tasks with Jenkins Integration for Jira automation features
RULE EDITOR
Create custom rules with the built in Rule Editor
- When: Select am event that triggers the rule
- If: Select a condition to execute the role based on the event data (optional)
- Then: Add an action(s) for the rule to perform
- Activate: Click on save to activate rule
EXECUTION
Rule logs
Executing rules automatically in only one step. Jenkins Integration Automation for Jira also tells you what happened. View all executions logs in one place.
- see everytime a rule is executed (all are logged)
- trace what a rule has (and has not) done
- know what conditions were (or were not) met
- get the outcome of those actions
USE CASE 1
Create issues based on
build results
Ever have a failed backup job build go unnoticed?
If you have jobs to update indexes or take backups that run on a schedule then Jenkins Integration Automation can alert you to a problem before it becomes critical.
These jobs are usually not linked to active development work.
Create issues based on
build results
For technical details read documentation page.
USE CASE 2
Transition an issue based on
build results
It is easy to forget to transition an issue to “In Progress” when a developer starts work on it. Sometimes it can even be difficult to transition the right issues to a QA or Pre-Production state in the issue workflow.
Forgetting to transition an issue to “In Progress” can often be solved in a scrum/update call. But it’s a lot of work to correct an issue that is not transitioned to the right issues to a QA or Pre-Production.
Transition an issue based on
build results
Automatically transition any issues for a synchronized build to the correct state (examples In Progress, QA, Done)
Automation at no extra cost
Jenkins Integration for Jira includes automation
Add automation to Jenkins Integration for Jira
Rules are the bases in which you will be able to configure automated actions to occur when specific events and conditions are met. The building blocks of rules are events, conditions and actions.
Events
Rules are the bases in which you will be able to configure automated actions to occur when specific events and conditions are met. The building blocks of rules are events, conditions and actions.
See documentation for more about event 
Conditions
Conditions narrow the scope of a rule. For example only perform the rule actions when the build has a specific outcome or when the build is of a specific job. Conditions can also be combined such as only performing an action for successful builds of a job.
See documentation for more about conditions
Actions
Actions are the building blocks of rules that will actually do something. They can create an issue, transition an issue or comment on an issue.
See documentation for more about actions
