Notification Rules | Targetprocess - Enterprise Agility Solution

Notification Rules

Notification rules allow you to keep track of changes to Targetprocess entities by configuring and sending notifications into targetprocess application or into email.  In the current version, only administrators of an instance can set up notifications for any other Targetprocess user.

Here you can define where to send notifications, who will receive them and what changes will trigger them.

How it works

Create a Set of Rules

Create a Notification Rule

Receive Notification

Delete Notification Rule or Set of Rules

Let's have a look at a simple example below. Whenever a User Story in Project 'Mobile' makes it to the state 'Planned' we would like to notify all the members of the Teams assigned to this User Story.

How It Works

The overall logic is based on Projects. You can create any number of notification rules that make sense for as many of the projects existing in the instance as you want. Each of these rules defines when, whom, and where to send the email notification to.

Set up notifications in just two steps:

  1. Create a set of rules for specific Projects
  2. Create notification rules inside these sets

Let's get deeper into these steps.

Create a Set of Rules

Go to Settings -> Notification rules page.

For example, you want to create rules for the ‘Mobile’ project.

Click on ‘Add a new set of rules’ button and select ‘Mobile’ project in the appeared 'Projects’ dropdown list. Then press ‘Next’.

You will see an empty container named ‘New set of rules’ claiming that There are no rules set for selected Projects.

You may want to update the list of selected Projects. For this, put the mouse over the Project name and click to edit.

You can do the same for the set's name.

Create a Notification Rule

As soon as you successfully create set of rules, let's go ahead and add notification rules.
Click on the ‘+ Add notification rule’ link to add the rules.
You will see three blocks: Action, Recipients, and Channel. The Actions selector is expanded by default.

Fill in Action, Entity types, Recipients and Channels. And voila, the rule is successfully created!

Rules work for entities and people assigned to Projects selected for the Set of Rules.

If Action, Entity type, or Recipient is empty the rule will not work.

Let’s have a closer look at the 3 blocks below:

Action Block

Contains a list of actions that will trigger a notification(will be widen in future):

  • Added: an entity is created in selected Projects
  • State changed: an entity changed its state. You can also specify the state in which entity should appear to trigger a notification.
  • User assigned: a person is assigned to an entity. If you select Project as entity type, then it's the user who assigned as project member.
  • Comment added: a comment is created in an entity
  • Attachment added: a file is attached to the entity

'Added' action can not be used for notifying the assigned person/team for newly created items, as assignment action takes place after the Entity creation action.

Entity Types Selector

Enumerates entity types. We now support seven types. We will work on increasing this list:

  • User Story
  • Bug
  • Task
  • Request
  • Feature
  • Epic
  • Portfolio Epic
  • Project

Recipients Block

Specifies a group of people who will receive notifications

    • Project Members: all people from the selected Projects in specific roles
The Project roles selector contains roles in which users are assigned to selected Projects. So if only QA and Developer users are working on the selected Projects then you'll see only these roles
    • Assigned Users: all people assigned to the selected entity types in specific roles
User(s) are assigned to an entity under some role. This role is considered by the rule.
    • Newly Assigned Users: means only the latest assigned user with a specific role. Available for 'User Assigned' action only.
It’s useful when you don’t want to send notifications about 'User assigned' to all of the previously assigned people but only to the user that was just assigned.
  • Assigned teams: all the people from the teams assigned to entity
  • Owners: the person that is the owner of an entity
  • Requesters: all the people assigned as Requester. The option is available for Request entity type only.
Actions, Entity types and Recipients fields depend on each other. Actions selector acts as the main field while Entity type and Recipients lists depend on it.

Channels Block

You can specify here where to send the notifications:


We send notifications into email specified in User's profile. Frequency is currently locked between 20 seconds and 3 minutes.

Let's see how we group notifications in emails:

  • After a change marked in rule happens for user, we wait for 20 seconds
  • If any other change occurs for this user we wait for additional 20 seconds
  • We repeat it until no new changes happen for the user in 20 seconds intervals or if 3 minutes elapses since the first notification
  • Then we group all the notifications and send via one email
Notifications feed

Notifications appear immediately in 'Notifications' feed located in targetprocess application, we don't group them.

Receive Notification

Let's test the added rule to confirm that it works.

When the action specified in the notification rule occurs then:

  • an email will be sent and it will look like this:
    Targetprocess Image
  • notification will be sent into targetprocess application:

Delete Notification Rule or Set of Rules

You can delete a notification rule by clicking the  ‘...’ menu that appears at the end of the corresponding rule. Hover over the rule and click the 'Delete' menu item.

The same goes for a set of rules. By deleting set of rules all the rules included in it will be deleted.


    • How can I migrate Process-based notifications into new ones?
    • We don’t cover all the cases from notifications configured via process settings for now. That’s why we ask you to set this up manually it is currently possible:
      - Create a rule from the Notification Rules interface.
      - Make sure that you receive the correct email.
      - Delete the original rule in Process notifications.
If you create notifications using the new Notification Rules interface and leave the same notifications in Process setup - you'll receive duplicate emails.
  • How do I disable notifications?
  • Currently, we do not have the option to disable all notifications so the only way to stop receiving them is to delete them.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.

Or contact
a sales representative

Get a live
product demo

Let one of our product specialists create your account
and shape Targetprocess for your company needs.