Automations
Automate recurring tasks in your projects with rules and triggers.
Contents
Automations
With automations, you save time by having recurring actions executed automatically. Define rules and let dVersum do the work.
How It Works
Automations follow the if-then principle:
IF a certain event occurs, THEN execute a certain action.
Creating an Automation
- Open a project
- Click on Settings (gear icon)
- Select Automations
- Click on New Automation
1. Choose a Trigger
Select the triggering event:
| Trigger | Description |
|---|---|
| Task created | When a new task is created |
| Task moved | When a task changes columns |
| Column reached | When a task reaches a specific column |
| Due date reached | When the due date is reached |
| Tag added | When a specific tag is added |
| Assignment changed | When the assigned person changes |
2. Conditions (Optional)
Add conditions to restrict the automation:
- Only if tag = specific tag
- Only if priority = High/Medium/Low
- Only if assigned to = specific person
- Only if title contains = specific text
3. Choose an Action
Select what should happen:
| Action | Description |
|---|---|
| Assign person | Automatically assign the task |
| Add tag | Automatically set a tag |
| Remove tag | Automatically remove a tag |
| Move to column | Move the task |
| Set due date | Set the due date |
| Set priority | Change the priority |
| Send notification | Notify a team member |
| Create subtask | Add a subtask |
Examples
Example 1: Automatic Assignment
IF a task with the tag "Bug" is created THEN assign it to Max Mustermann
Setup:
- Trigger: Task created
- Condition: Tag = "Bug"
- Action: Assign to Max Mustermann
Example 2: Notification on DONE
IF a task is moved to DONE THEN notify the project manager
Setup:
- Trigger: Column reached = DONE
- Action: Notification to project manager
Example 3: Priority on Due Date
IF a task is due in 2 days THEN set priority to High
Setup:
- Trigger: Due in 2 days
- Action: Priority = High
Example 4: QA Workflow
IF a task is moved to REVIEW THEN assign it to the QA team AND add the tag "QA-Check"
Setup:
- Trigger: Column reached = REVIEW
- Action 1: Assign to QA team
- Action 2: Add tag = "QA-Check"
Multiple Actions
An automation can execute multiple actions:
- Create the automation
- Click on + Add Action
- Add as many actions as needed
All actions are executed simultaneously.
Managing Automations
Enable/Disable
- Go to the project automations
- Click the toggle next to the automation
- Disabled automations will not be executed
Edit
- Click on the automation
- Change triggers, conditions, or actions
- Save
Delete
- Click on ... next to the automation
- Select Delete
- Confirm
Automation Log
See which automations have been executed:
- Go to Settings -> Automations
- Click on View Log
- You will see:
- Time of execution
- Affected task
- Executed actions
- Status (Success/Error)
Templates
Common automations as templates:
| Template | Description |
|---|---|
| Close sprint | Move all DONE tasks to archive |
| SLA warning | Notify when a deadline is about to be missed |
| Onboarding | Create subtasks for new team members |
| Review cycle | Automatic review workflow |
Limits and Restrictions
- Maximum 20 automations per project
- Maximum 5 actions per automation
- Automations run at most once per minute for the same task
- No infinite loops - Actions do not trigger further automations
Best Practices
- Start simple - Begin with simple rules
- Test - Check new automations with test tasks
- Document - Give automations descriptive names
- Don't overdo it - Too many automations can be confusing
- Review regularly - Are all automations still relevant?
Troubleshooting
Automation is not executing
- Is the automation enabled?
- Do all conditions match?
- Has the action already taken place?
- Check the log for errors
Unexpected behavior
- Check the order of automations
- Are there conflicting rules?
- Disable automations one by one for testing
Last updated: 4/6/2026