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

Nest smart values in Automation

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Using Automation for Jira, I'd like to nest smart values as follows:

      {{project.properties.issue.component}}
      

      Assuming a project property like this:

      {
      key: "Component A",
      value: "5caccd8a1608c412138787e3"
      }
      

      And also support complex JSON objects stored in entity properties, like so:

      {{project.properties.issue.component.approver2}}
      

      The project property would look like this:

      {
          key: "Component B",
          value: {
             "approver1": "5cc8aeebcbbec211ec62a0ec",
             "approver2": "5e7bf681dde7030c4f20dec6"
          }
      }
      

      But even better would be if we could have a single Project property with these mappings, like so:

      {
          key: "MappingList",
          value: {
              "Component A" : {
                     "approver1": "zyx",
                     "approver2": "wvu",
              },
              "Component B" : {
              "approver1": "abc",
                      "approver2": "xyz",
              },
                     "Component B" : {
                    "approver1": "def",
             "approver2": "ghi",
            },
            }
      }
      

      And we could reference it like this:

      {{project.properties."MappingList".{{issue.component}}.approver2}}

      Introducing nested smart values would be a great addition to be used in conjunction with the create lookup table feature. For example:

      {{Lookuptable.get("{{smartvalue}}")}}

              Unassigned Unassigned
              19d5cab36386 Raf (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: