If you are expecting an email from Kordiam that never arrives, or you receive more emails than you expected, three settings are involved. Working through them in this order usually explains it.
1. Your own settings decide what is worth an email
Under "My Settings" in the "Notifications" section you define two things:
- Cases — when you are a possible recipient, for example because you are the assignee of a task.
- Trigger actions — which events reach you: a new entry, a change, or a removal. For changes you can also limit this to specific fields using the "Triggers" drop-down.
Both have to be satisfied. Details on every option are in Granular Notification settings.
2. The "Triggers" selection is the strictest filter
If a field is not part of your "Triggers" selection, a change to that field does not produce an email. This applies no matter who saved the change.
This is the most common reason for missing notifications. If in doubt, set "Triggers" to "All" and narrow it down again from there.
3. The "Inform user" box only affects the assignee case
When someone saves a change, the "Inform user" box in the Story Card decides who is informed about that particular save. The box sits beneath the names of the people who have a task on the story. It is not displayed beneath your own name, but other people do see it there.
- If the box is unchecked, the email you would have received as the assignee is dropped. If you created or edited the story yourself and have the matching case activated, you still receive the email.
- If the box is checked, you only receive an email if the change also passes your own "Triggers" selection. Checking the box cannot produce an email for a field you have not selected.
In other words: the box lets colleagues control who is informed on the basis of a task assignment. What is worth an email to you in the first place is defined solely by your own settings, and nobody can widen those.
Task confirmations work independently of all of this
The "Ask for confirmation" box in the Story Card is not part of the notification settings described above. If the box is checked when the change is saved, the assignee always receives the request — regardless of their own notification settings, and even if they have selected "No notifications".
Whether the box appears at all, whether it can be selected per task, or whether it is already selected by default is controlled by the "Task confirmation" setting in the user profile. Administrators can adjust this per user on the Users page.
Note on "Only for changes to my tasks, not for other updates to the story"
This option does not currently limit your notifications to your own tasks in all situations. Depending on your "Triggers" selection you may also receive notifications about other people's tasks on the same story, or about new tasks assigned to someone else.
To keep the number of notifications low, we currently recommend working with the "Triggers" selection instead and limiting it to the fields that matter to you.
We are working on this option. This article will be updated as soon as the behaviour changes.
Comments
0 comments
Please sign in to leave a comment.