Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-17244

JSM Operations: Unable to change order of New Alert event notification rules under

XMLWordPrintable

      Issue Summary

      Customers are unable to reorder the "New Alert" event notification rule within their user notification profile. This prevents users from customizing the order in which notification rules are evaluated and applied, potentially impacting how and when they receive critical alert notifications.

      Steps to Reproduce

      1. Log in to yoursite.atlassian.net and explore the user notification page, and select the alert notification settings.
      2. Navigate to your profile and open the Alert notifications tab.
      3. Create A, B, C and D, and filter conditions.
      4. Attempt to reorder the notification rules for the "New Alert" event (e.g., by dragging and dropping or using any available UI controls). ie, Move D to the top of the list and refresh. You'll notice that has been restored to the top position.
      5. Observe that the UI allows you to move or reorder the "New Alert" rule, but when you refresh the page, the changes are reverted back. 

      Expected Results

      Users should be able to reorder notification rules for the "New Alert" event, allowing them to prioritize which rules are evaluated first according to their preferences.

      Actual Results

      The "New Alert" notification rule cannot be reordered. The UI does not respect changes the user makes by either (drag-and-drop, up/down arrows, etc.) the rule to their preferences.

      The below exception is thrown in the xxxxxxx.log file:

      ...
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              f4b0279555c4 John Yak
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: