FAQ

Setup

Who can set up rules?
Jira administrators. They add rules in Jira’s workflow editor and use the app’s admin page. Project administrators can see the rule history of work items in their projects.
Do I need to write code?
No. Each rule has its own screen, and the no-code builder covers conditions and validators by field, operator and value. A Jira expression can be typed where you want one.
Where is the admin page?
In Jira, open Settings, then Apps, and choose Simple Workflow Automation in the left menu.
Why is my new rule not on the Rules tab?
The Rules tab lists what the last scan found. Choose Scan workflows to read your workflows again.

Running rules

Whose permissions apply when a rule runs?
You choose for most post-functions and for event and scheduled actions: the person who made the move, the app, or a named person. When it runs as a person, Jira checks that person’s permissions.
Does a failed post-function stop the move?
No. Post-functions run after the move, so it stays done. Run history shows what failed and why.
Can I try a rule without changing work?
Yes. Many rule screens can test a rule on a work item with nothing saved. A dry run, per rule, per workflow or for the whole site, logs what would happen and changes nothing.
Can I switch one rule off?
Yes. Each rule has its own switch on the Rules tab, so you can turn it off without deleting it.
How do I see what a rule did?
Run history on the admin page lists each run with the time, the result, a plain reason and how long it took. You can export it as CSV, up to 5,000 rows.

Projects and email

Does it work in team-managed projects?
Yes, with limits. One condition, four validators and most post-functions work there, and post-functions run only as the person who made the move.
Can email go to people without a Jira account?
Yes, on sites with Jira Service Management. A plain address is added as a service project customer the first time it is used. People who hide their address from apps are skipped.

Data

Where does the app keep its data?
In Atlassian’s Forge storage for this app: rule settings, run history, rule change history, shared, event and scheduled actions. It runs on Atlassian Forge and has no servers of its own.
How long is run history kept?
Ninety days from each run. Rule change history is kept 90 days too.

More: Troubleshooting and Limits to expect.


Need help with Simple Workflow Automation? Contact us