Discover Jira Cloud products
Learn more about Jira Cloud products, features, plans, and migration.
Here’s how old rules in company-managed projects map to new rules. Use the table below to find the adjacent new rule in the new workflow editor.
Old rule | New rule |
---|---|
| Restrict who can move an issue |
| Restrict to when an issue has been through a specific status |
| Validate that people have a specific permission |
(This isn’t a rule in the old workflow editor, but it is in the new workflow editor.) | Show a screen |
| Copy the value of one field to another |
| Update an issue field |
Status mapping
Properties
Shared transitions
Custom events
Even if you use some of these features, you can still continue with the EAP. It just means you won’t be able to add them from the new workflow editor. To add these unavailable features during the EAP, you’ll need to access the old workflow editor, which you’ll be able to do from the new workflow editor.
Note that we’ll add many of these rules as we keep improving the new workflow editor.
User Is In Group Custom Field
User Is In Custom field
Hide From User Condition
Always False Condition
Value Field
Compare Number Custom Field
Sub-Task Blocking Condition
Separation of Duties condition
Field Required Validator
Field has been modified Validator
Field has single value Validator
Regular Expression Check
Date Compare Validator
Date Window Validator
Previous State Validator
Parent Status Validator
Assign to Current User
Assign to Lead Developer
Assign to Reporter
Trigger a Webhook
Set issue security level based on user's project role
Only Bamboo Notifications Workflow Condition
Create Crucible Review Workflow Function
Looped transitions
Exporting workflows
Triggers
Was this helpful?