When editing work item (Adding organisation) using Lookup table action not triggering organization added notifications

XMLWordPrintable

    • Severity 3 - Minor
    • Jira Service Management

      Issue Summary

      When editing work item (Adding organisation) using Lookup table action not triggering organization added notifications

      Steps to Reproduce

       Create an automation rule to update the Organization field using a lookup table, as shown below:

      • Create lookup table (ProjectOrgMap) with below
       

      key : DEMO
      Value 2

      • In Edit Work item use below smart value (Make sure to select Send email checkbox)
       {
      "fields": {
      "Organizations": [
      {{ProjectOrgMap.get(issue.project.key).asNumber}}
      ]
      }
      }

       

               

      • While the rule successfully adds the Organisation to the ticket, the “Organisation added” notification is not triggered in this setup.
      • However, the notification is sent as expected when the same update is performed within an If/Else condition block.
      {
        "update": {
          "customfield_10002": [
            { "add": 1 }
          ]
        }
      } 

      Expected Results

      The "Organisation added” notification should be triggered

      Actual Results

       The “Organisation added” notification is not triggered

      Workaround

      • Use an If/Else block in the automation rule instead of a look-up table to ensure the notification is triggered.

      OR

      • Add a “Send comment” action to the rule to notify the customer after updating the Organisation field if using the lookup table.

        1. Screenshot 2026-04-17 at 7.49.48 PM.png
          143 kB
          Rakshitha G S
        2. Screenshot 2026-04-17 at 7.55.40 PM.png
          124 kB
          Rakshitha G S

              Assignee:
              Unassigned
              Reporter:
              Rakshitha G S
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: