111 views

Description

User creates multiple subscriptions for the same notification and the same device with different conditions. The user is included as a recipient for one of the subscriptions but not another even when the conditions pass. The order the subscriptions are evaluated are not known.

Steps to Reproduce

 

  1. Create a new notification that is subscribable (incident table / update / condition if desired).

  2. Create a new personal notification with a condition of short_description contains TEST1.

  3. Create a new personal notification with a condition of short_description contains TEST2.

    Both of these subscriptions are for the newly created notification and for the same user.

  4. Update an incident, making the Short description TEST1.

  5. Update another incident, making the short description TEST2.

  6. If there are conditions on the notification, make sure they are met on any updates.

    Note that you can also preview the notification and select the different incidents if desired.

    The user is included for only one of these records/subscriptions. The other record excludes the user.

 

Workaround

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make these decisions lightly, and we apologize for any inconvenience. 

Please use either of these workaround options:

  • Have all filters on a single subscription preference. This will create only one email, as designed.
  • Create more notifications with some of the filters on the notifications. This enables multiple emails to be created for a single insert/update. Users will need to subscribe to each notification and further filtering can be done by the user at this time as well.

 


Related Problem: PRB1236857

Seen In

Jakarta

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-03-21 07:11:28
Published:2018-03-21