Jira Workflow Fundamentals

JSU Automation Suite for Jira Workflows is an automation tool for Jira administrators and it is expected that you are familiar with creating and editing workflows and customizing Jira projects to meet the needs of your teams.

If you haven't edited a workflow before, we have included a short summary of Jira’s workflow fundamentals here. This will help you see where JSU fits in your workflows and how our modules are combined to build versatile and powerful automation rules. If you want to go straight to adding rules to a project workflow, see Edit a Jira workflow.

What is a workflow?

Simply put, a Jira workflow is a set of statuses and transitions that represent the path that an issue or piece of work progresses through from start to finish. Every team will have its own definition of done, and how they get there. 

A status indicates where in the journey the issue is, for example, In Progress or Awaiting Approval.

A transition is a movement or action from one status to another, such as In Progress to Publish (Done).

Issues will also include an assignee (user responsible for an action or issue) and a resolution for a closed issue, for example, Canceled, Fixed, or Can't reproduce. 

Within a workflow, you can add rules to determine if, and how issues are allowed to transition to another status and what should happen afterward; these are called Conditions, Validators, and Post Functions.



 

 

Conditions

Conditions determine if a workflow transition is available for the current user. For example, in an Approvals workflow, you can set a condition so that only certain users can access the Approve/Reject transition. You can apply JSU's User is any Users condition to restrict a transition to specific users.

Condition applied to an Approve transition in a Jira issue

 

 

Validators

Validators check the field value of the issue and reject the transition if the criteria are not met. For example, in an Approvals workflow, a value in a Budget field can be mandatory. You can set also define a message to display to users when the transition is rejected. Validators can also be applied to ensure that field values are entered in the correct format using regular expressions. 

Jira issue field highlighted as mandatory

 

 

Post functions

Post functions modify data in Jira after a transition is performed. In this example, JSU's Create a Linked Issue post function is used to create subtasks in a parent issue automatically. With JSU post functions you can add a condition (or 'precondition') to prevent the post function from running if criteria are not met. See JSU's Preconditions to learn more.

 

Animation of sub-tasks automatically created in a Jira issue

 

 

Workflow automation with JSU

A simple, no-code way to extend Jira workflows

What if you need an easy way to accomplish even more in Jira? What if you want to automate processes to empower your teams to work faster and more efficiently? JSU has the answer to creating powerful workflow rules. With JSU, you can easily go beyond Jira’s native functionality to reduce friction and increase productivity. Our flexible set of post functions and conditions can be combined to create powerful, fine-tuned automation rules without any coding.

See JSU in Action to learn how quickly you can build your first JSU automation!