Skip to main content
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Custom Events

  1. Last updated
  2. Save as PDF

Custom Events are triggers and actions that allow you to extend AgilePlace automations beyond the standard capabilities. With Custom Events, you can create automations that respond to specific circumstances on your board or within your cards.

Types of Custom Events

AgilePlace supports two types of Custom Events:

  1. Card-level Custom Events: These events trigger automations based on specific events happening to individual cards, allowing for targeted automation on particular cards.

  2. Board-level Custom Events: When enabled using the "Allow Board Event" checkbox, these events can be triggered at the board level rather than for a specific card. Board-level events will run against any cards that meet the specified criteria, similar to how scheduled automations run. This option provides broader application of your automation rules.

Configuration Instructions

Creating a Custom Event Action

To set up a Custom Event action:

1. Navigate to your board settings
2. Select "Card Automation" from the menu
3. Click "Create New Automation"
4. Select the condition that will initiate your custom event
5. Choose the target type (parent cards or child cards)
6. Enter a unique name for your custom event (e.g., "epic_backlog")
7. Save your configuration

Setting Up a Custom Event Trigger

To create an automation that responds to a Custom Event:

1. Navigate to your board settings
2. Select "Card Automation" from the menu
3. Click "Create New Automation"
4. Select "Custom Event" as the trigger type
5. Enter the exact name of the custom event you want to monitor
6. Configure the action to be performed when the event occurs
7. Save your automation

Example: Parent-Child Card Status Mirroring

You can use Custom Events to mirror card movements between parent and child cards:

1. Create the trigger automation: When a child Epic card moves to "Epic Backlog", generate a custom event called "epic_backlog"

2. Create the listener automation: When the "epic_backlog" event is detected, move the associated parent Initiative card to its corresponding lane

This ensures that parent cards accurately reflect the status of their child cards throughout your workflow.

Best Practices

  • Use descriptive names for your custom events to maintain clarity
  • Document your custom events to help team members understand your automation structure
  • Test your automations thoroughly before relying on them in production
  • Monitor custom event usage to avoid hitting rate limits