The "View All Items" privilege is ignored for notifications if the privilege is only granted to a user via a group that inherits the privilege from a role. If the user is added to the role directly, the privilege is honored and he or she will receive the notification .
In 10.1 there may be instances where user fields are not sent properly in notifications , and the place where they belong in the notification is left blank. ERROR [FileTemplate] -- failed to render tag "FIELDVALUE" with parameters
Currently display value for any relational field is rendered as [issue id]: [title]. However, any table has "display value format" property, which defines how value is rendered based on table fields.
If a user isn't already in the SaaS system upon getting an e-mail notification , clicking on the link will force them to re-authenticate, and take them to the home page rather than directly to the item.
Two fields share the same field name (DB Field Name is different, of course). One is a text field and the other is a single selection field. When creating notification rules, the fields are listed in the following order:
If you use $CHANGES() in a notification template, then the notification will not contain the content of any append-only journal fields. You may work round this problem by specifically adding the field to the list of fields sent in the notification , when it will appear correctly, provided that the recipient has permissions to view the field.
- subscribe this user to the Any Item Changes State (or any other relevant) notification for this project - modify the notification template making sure the $NOTES() function is contained. - as a different user create a new item in this project.
