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

  1. Open a project
  2. Click on Settings (gear icon)
  3. Select Automations
  4. Click on New Automation

1. Choose a Trigger

Select the triggering event:

TriggerDescription
Task createdWhen a new task is created
Task movedWhen a task changes columns
Column reachedWhen a task reaches a specific column
Due date reachedWhen the due date is reached
Tag addedWhen a specific tag is added
Assignment changedWhen 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:

ActionDescription
Assign personAutomatically assign the task
Add tagAutomatically set a tag
Remove tagAutomatically remove a tag
Move to columnMove the task
Set due dateSet the due date
Set priorityChange the priority
Send notificationNotify a team member
Create subtaskAdd a subtask

Examples

Example 1: Automatic Assignment

IF a task with the tag "Bug" is created THEN assign it to Max Mustermann

Setup:

  1. Trigger: Task created
  2. Condition: Tag = "Bug"
  3. Action: Assign to Max Mustermann

Example 2: Notification on DONE

IF a task is moved to DONE THEN notify the project manager

Setup:

  1. Trigger: Column reached = DONE
  2. 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:

  1. Trigger: Due in 2 days
  2. 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:

  1. Trigger: Column reached = REVIEW
  2. Action 1: Assign to QA team
  3. Action 2: Add tag = "QA-Check"

Multiple Actions

An automation can execute multiple actions:

  1. Create the automation
  2. Click on + Add Action
  3. Add as many actions as needed

All actions are executed simultaneously.

Managing Automations

Enable/Disable

  1. Go to the project automations
  2. Click the toggle next to the automation
  3. Disabled automations will not be executed

Edit

  1. Click on the automation
  2. Change triggers, conditions, or actions
  3. Save

Delete

  1. Click on ... next to the automation
  2. Select Delete
  3. Confirm

Automation Log

See which automations have been executed:

  1. Go to Settings -> Automations
  2. Click on View Log
  3. You will see:
    • Time of execution
    • Affected task
    • Executed actions
    • Status (Success/Error)

Templates

Common automations as templates:

TemplateDescription
Close sprintMove all DONE tasks to archive
SLA warningNotify when a deadline is about to be missed
OnboardingCreate subtasks for new team members
Review cycleAutomatic 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

  1. Start simple - Begin with simple rules
  2. Test - Check new automations with test tasks
  3. Document - Give automations descriptive names
  4. Don't overdo it - Too many automations can be confusing
  5. Review regularly - Are all automations still relevant?

Troubleshooting

Automation is not executing

  1. Is the automation enabled?
  2. Do all conditions match?
  3. Has the action already taken place?
  4. Check the log for errors

Unexpected behavior

  1. Check the order of automations
  2. Are there conflicting rules?
  3. Disable automations one by one for testing

Last updated: 4/6/2026