Simple Workflow Automation is a Forge app for Jira Cloud. It adds workflow rules to Jira’s workflow editor, and an admin page where you see every rule, why it did or did not run, and whether anything is broken.
What it adds
| Part | What it does | Where you set it up |
|---|---|---|
| Conditions (5) | Hide a transition unless something is true: the status, linked work items, the person, an expression or the time. | Jira’s workflow editor |
| Validators (11) | Refuse a move, with a message, until fields are filled in, a file or comment is added, a format or date check passes, and more. | Jira’s workflow editor |
| Post-functions (24) | Change things after a move: set, clear and copy fields, comment, create, assign, link, email and more. | Jira’s workflow editor |
| Event-based actions | Run a shared action when something happens in Jira, such as a comment, a version release or a sprint start. | Admin page, Events tab |
| Scheduled actions | Run steps once a day on the work items a search finds. | Admin page, Scheduled actions tab |
| Shared actions | A named list of steps, kept in one place and used by many transitions, event actions and scheduled actions. | Workflow editor and admin page |
In Jira, each rule’s name starts with Simple Workflow Automation -, for example Simple Workflow Automation - Required comment. Each rule has its own screen, and conditions and validators can be built with the no-code builder.
Ways to stay in control
- Run as: choose who most actions run as, so Jira checks that person’s permissions.
- Dry run: a rule, a workflow or the whole site works out what it would do and changes nothing.
- Switch a rule off, and test it: one switch per rule, and a test on a real work item that saves nothing.
- Run history and History: every run with a plain reason, and who changed which rule.
Who it is for
Jira administrators set up rules and use the admin page. Project administrators can see the rule history of a work item in their projects. Everyone else meets the rules as they move work: a hidden transition, a validator message, or a change made after the move.
What it does not do
- It runs only on Jira Cloud.
- Post-functions run after the move, so a failed post-function never undoes or blocks the move. The reason is shown in run history.
- Conditions and validators run inside Jira, so they are not listed in run history.
Related pages
Need help with Simple Workflow Automation? Contact us