Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16218

Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value.

      Summary

      Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value. This issue does not affect JSM customer notifications.

      Behaviour in JSM 5.13 and below

      Behaviour in JSM 5.14+

       

      Steps to Reproduce

      1. Install Jira Service Management 10.1.1
      2. Configure outbound email
      3. Create a Jira issue with an Asset field
      4. Verify the issue created the mail notification

      Expected Results

      The object label will be displayed:

      Behaviour in JSM 5.13 and below

       

      Actual Results

      The object key is displayed instead of the label:

      Behaviour in JSM 5.14+

       

      Workaround

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

        1. image-2025-05-20-09-10-17-788.png
          114 kB
          Rodrigo Jose Zaparoli
        2. image-2025-05-20-09-10-32-967.png
          95 kB
          Rodrigo Jose Zaparoli
        3. image-2025-05-20-09-10-47-992.png
          114 kB
          Rodrigo Jose Zaparoli
        4. image-2025-05-20-09-10-57-500.png
          95 kB
          Rodrigo Jose Zaparoli

            [JSDSERVER-16218] Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value.

            Benjamin Suess made changes -
            Status Original: Short Term Backlog [ 12074 ] New: Gathering Impact [ 12072 ]
            Benjamin Suess made changes -
            Affects Version/s New: 5.14.0 [ 106300 ]
            Benjamin Suess made changes -
            Description Original: h3. Summary

            Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value. This issue does not affect JSM customer notifications.
            h3. Behaviour in JSM 10.0.0 and below

            !image-2025-05-20-09-10-17-788.png|width=266,height=198!
            h3. Behaviour in JSM 10.1.1+

            !image-2025-05-20-09-10-32-967.png|width=381,height=276!

             
            h3. Steps to Reproduce
             # Install Jira Service Management 10.1.1
             # Configure outbound email
             # Create a Jira issue with an Asset field
             # Verify the issue created the mail notification

            h3. Expected Results

            The object label will be displayed:
            h3. Behaviour in JSM 10.0.0 and below

            !image-2025-05-20-09-10-47-992.png|width=167,height=124!

             
            h3. Actual Results

            The object key is displayed instead of the label:
            h3. Behaviour in JSM 10.1.1+

            !image-2025-05-20-09-10-57-500.png|width=251,height=182!

             
            h3. Workaround

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

            Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value. This issue does not affect JSM customer notifications.
            h3. Behaviour in JSM 5.13 and below

            !image-2025-05-20-09-10-17-788.png|width=266,height=198!
            h3. Behaviour in JSM 5.14+

            !image-2025-05-20-09-10-32-967.png|width=381,height=276!

             
            h3. Steps to Reproduce
             # Install Jira Service Management 10.1.1
             # Configure outbound email
             # Create a Jira issue with an Asset field
             # Verify the issue created the mail notification

            h3. Expected Results

            The object label will be displayed:
            h3. Behaviour in JSM 5.13 and below

            !image-2025-05-20-09-10-47-992.png|width=167,height=124!

             
            h3. Actual Results

            The object key is displayed instead of the label:
            h3. Behaviour in JSM 5.14+

            !image-2025-05-20-09-10-57-500.png|width=251,height=182!

             
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            Benjamin Suess made changes -
            Affects Version/s New: 10.0.0 [ 107096 ]
            Bartosz Ornatowski made changes -
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            Rodrigo Jose Zaparoli made changes -
            Description Original: h3. Summary

            Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value. This issue does not affect JSM customer notifications.
            h3. Behaviour in JSM 10.0.0 and below
            h3. [!https://api.media.atlassian.com/file/1cac8d26-dae2-47fb-9299-8a91b725cee5/binary?token=eyJraWQiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzLzhhdXRtMTNuamQwNmE5NjEiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiJtZWRpYSIsImNsaWVudElkIjoiOTExYjVmNDEtZDYzNS00NWU4LTkzZjctY2MxZDU2ZWEzMGFiIiwiYWNjZXNzIjp7InVybjpmaWxlc3RvcmU6ZmlsZToqIjpbImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNvbGxlY3Rpb246ODYzMDYxNyI6WyJyZWFkIiwidXBkYXRlIiwiaW5zZXJ0Il0sInVybjpmaWxlc3RvcmU6dXBsb2FkOioiOlsicmVhZCIsImNyZWF0ZSIsInVwZGF0ZSIsImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOnVwbG9hZCI6WyJjcmVhdGUiXSwidXJuOmZpbGVzdG9yZTpmaWxlIjpbImNyZWF0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNodW5rOioiOlsicmVhZCIsImNyZWF0ZSJdfSwibmJmIjoxNzQ3NjY4MzA1LCJpc3MiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzIiwiZXhwIjoxNzQ3Njc5MTA1LCJpYXQiOjE3NDc2NjgzMDUsImp0aSI6IjZlZGZkNjJlLWQ2ZTctNDkwYS05M2MyLWM3ZDQ3NDlmN2ZlMyJ9.DpdiRP_tcRCAyKt1zTwLUrkOyoUkSgKSB1iqwiEIqGVnERf7WFw3pj5zexPJqFsGs1rse-xsFSkdHXh5Z9BQOY8N6BJnSu__pEaQ3j9_EOj8eYSvIxjcCNP2zRA_3At_RLF8A3sem9EJ2-z2wQFi0AGBmaza-uN0HgO_E6fJvCkHVHWNDAFrU4c8v01ZkH6DucoQJquhLIExyVzge_4fJKp3rd4Declub2gRGbdJdlrnMGHPk_HzcAr7wvHUi7Vs5Cvu2QelRSrEUk_fniAEC8GbeVWn-chqgpfnqbvUoF-ZraZVCriwBJSXp6yTlz2DvsX9yVJjJCupzuKl4yYg0w&client=911b5f41-d635-45e8-93f7-cc1d56ea30ab&collection=8630617&max-age=43200&dl=true|width=376,height=280!|https://transfer.atlassian.com/preview/8630617/attachment/1cac8d26-dae2-47fb-9299-8a91b725cee5]
            h3. Behaviour in JSM 10.1.1+
            h3. [!https://api.media.atlassian.com/file/40651c3b-3701-438e-84d8-5c53a4d3dc19/binary?token=eyJraWQiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzLzhhdXRtMTNuamQwNmE5NjEiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiJtZWRpYSIsImNsaWVudElkIjoiOTExYjVmNDEtZDYzNS00NWU4LTkzZjctY2MxZDU2ZWEzMGFiIiwiYWNjZXNzIjp7InVybjpmaWxlc3RvcmU6ZmlsZToqIjpbImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNvbGxlY3Rpb246ODYzMDYxNyI6WyJyZWFkIiwidXBkYXRlIiwiaW5zZXJ0Il0sInVybjpmaWxlc3RvcmU6dXBsb2FkOioiOlsicmVhZCIsImNyZWF0ZSIsInVwZGF0ZSIsImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOnVwbG9hZCI6WyJjcmVhdGUiXSwidXJuOmZpbGVzdG9yZTpmaWxlIjpbImNyZWF0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNodW5rOioiOlsicmVhZCIsImNyZWF0ZSJdfSwibmJmIjoxNzQ3NjY4MzA1LCJpc3MiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzIiwiZXhwIjoxNzQ3Njc5MTA1LCJpYXQiOjE3NDc2NjgzMDUsImp0aSI6IjZlZGZkNjJlLWQ2ZTctNDkwYS05M2MyLWM3ZDQ3NDlmN2ZlMyJ9.DpdiRP_tcRCAyKt1zTwLUrkOyoUkSgKSB1iqwiEIqGVnERf7WFw3pj5zexPJqFsGs1rse-xsFSkdHXh5Z9BQOY8N6BJnSu__pEaQ3j9_EOj8eYSvIxjcCNP2zRA_3At_RLF8A3sem9EJ2-z2wQFi0AGBmaza-uN0HgO_E6fJvCkHVHWNDAFrU4c8v01ZkH6DucoQJquhLIExyVzge_4fJKp3rd4Declub2gRGbdJdlrnMGHPk_HzcAr7wvHUi7Vs5Cvu2QelRSrEUk_fniAEC8GbeVWn-chqgpfnqbvUoF-ZraZVCriwBJSXp6yTlz2DvsX9yVJjJCupzuKl4yYg0w&client=911b5f41-d635-45e8-93f7-cc1d56ea30ab&collection=8630617&max-age=43200&dl=true|width=328,height=238!|https://transfer.atlassian.com/preview/8630617/attachment/40651c3b-3701-438e-84d8-5c53a4d3dc19]
            h3. Steps to Reproduce
             # Install Jira Service Management 10.1.1
             # Configure outbound email
             # Create a Jira issue with an Asset field
             # Verify the issue created the mail notification

            h3. Expected Results

            The object label will be displayed:
            h3. Behaviour in JSM 10.0.0 and below
            h3. [!https://api.media.atlassian.com/file/1cac8d26-dae2-47fb-9299-8a91b725cee5/binary?token=eyJraWQiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzLzhhdXRtMTNuamQwNmE5NjEiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiJtZWRpYSIsImNsaWVudElkIjoiOTExYjVmNDEtZDYzNS00NWU4LTkzZjctY2MxZDU2ZWEzMGFiIiwiYWNjZXNzIjp7InVybjpmaWxlc3RvcmU6ZmlsZToqIjpbImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNvbGxlY3Rpb246ODYzMDYxNyI6WyJyZWFkIiwidXBkYXRlIiwiaW5zZXJ0Il0sInVybjpmaWxlc3RvcmU6dXBsb2FkOioiOlsicmVhZCIsImNyZWF0ZSIsInVwZGF0ZSIsImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOnVwbG9hZCI6WyJjcmVhdGUiXSwidXJuOmZpbGVzdG9yZTpmaWxlIjpbImNyZWF0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNodW5rOioiOlsicmVhZCIsImNyZWF0ZSJdfSwibmJmIjoxNzQ3NjY4MzA1LCJpc3MiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzIiwiZXhwIjoxNzQ3Njc5MTA1LCJpYXQiOjE3NDc2NjgzMDUsImp0aSI6IjZlZGZkNjJlLWQ2ZTctNDkwYS05M2MyLWM3ZDQ3NDlmN2ZlMyJ9.DpdiRP_tcRCAyKt1zTwLUrkOyoUkSgKSB1iqwiEIqGVnERf7WFw3pj5zexPJqFsGs1rse-xsFSkdHXh5Z9BQOY8N6BJnSu__pEaQ3j9_EOj8eYSvIxjcCNP2zRA_3At_RLF8A3sem9EJ2-z2wQFi0AGBmaza-uN0HgO_E6fJvCkHVHWNDAFrU4c8v01ZkH6DucoQJquhLIExyVzge_4fJKp3rd4Declub2gRGbdJdlrnMGHPk_HzcAr7wvHUi7Vs5Cvu2QelRSrEUk_fniAEC8GbeVWn-chqgpfnqbvUoF-ZraZVCriwBJSXp6yTlz2DvsX9yVJjJCupzuKl4yYg0w&client=911b5f41-d635-45e8-93f7-cc1d56ea30ab&collection=8630617&max-age=43200&dl=true|width=368,height=274!|https://transfer.atlassian.com/preview/8630617/attachment/1cac8d26-dae2-47fb-9299-8a91b725cee5]

             
            h3. Actual Results

            The object key is displayed instead of the label:
            h3. Behaviour in JSM 10.1.1+
            h3. [!https://api.media.atlassian.com/file/40651c3b-3701-438e-84d8-5c53a4d3dc19/binary?token=eyJraWQiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzLzhhdXRtMTNuamQwNmE5NjEiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiJtZWRpYSIsImNsaWVudElkIjoiOTExYjVmNDEtZDYzNS00NWU4LTkzZjctY2MxZDU2ZWEzMGFiIiwiYWNjZXNzIjp7InVybjpmaWxlc3RvcmU6ZmlsZToqIjpbImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNvbGxlY3Rpb246ODYzMDYxNyI6WyJyZWFkIiwidXBkYXRlIiwiaW5zZXJ0Il0sInVybjpmaWxlc3RvcmU6dXBsb2FkOioiOlsicmVhZCIsImNyZWF0ZSIsInVwZGF0ZSIsImRlbGV0ZSJdLCJ1cm46ZmlsZXN0b3JlOnVwbG9hZCI6WyJjcmVhdGUiXSwidXJuOmZpbGVzdG9yZTpmaWxlIjpbImNyZWF0ZSJdLCJ1cm46ZmlsZXN0b3JlOmNodW5rOioiOlsicmVhZCIsImNyZWF0ZSJdfSwibmJmIjoxNzQ3NjY4MzA1LCJpc3MiOiJtaWNyb3MtZ3JvdXAvY3N0LWF0dGFjaG1lbnRzIiwiZXhwIjoxNzQ3Njc5MTA1LCJpYXQiOjE3NDc2NjgzMDUsImp0aSI6IjZlZGZkNjJlLWQ2ZTctNDkwYS05M2MyLWM3ZDQ3NDlmN2ZlMyJ9.DpdiRP_tcRCAyKt1zTwLUrkOyoUkSgKSB1iqwiEIqGVnERf7WFw3pj5zexPJqFsGs1rse-xsFSkdHXh5Z9BQOY8N6BJnSu__pEaQ3j9_EOj8eYSvIxjcCNP2zRA_3At_RLF8A3sem9EJ2-z2wQFi0AGBmaza-uN0HgO_E6fJvCkHVHWNDAFrU4c8v01ZkH6DucoQJquhLIExyVzge_4fJKp3rd4Declub2gRGbdJdlrnMGHPk_HzcAr7wvHUi7Vs5Cvu2QelRSrEUk_fniAEC8GbeVWn-chqgpfnqbvUoF-ZraZVCriwBJSXp6yTlz2DvsX9yVJjJCupzuKl4yYg0w&client=911b5f41-d635-45e8-93f7-cc1d56ea30ab&collection=8630617&max-age=43200&dl=true|width=370,height=269!|https://transfer.atlassian.com/preview/8630617/attachment/40651c3b-3701-438e-84d8-5c53a4d3dc19]

             
            h3. Workaround

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

            Asset fields, in email notifications from the notification scheme, are displaying as object keys instead of the label value. This issue does not affect JSM customer notifications.
            h3. Behaviour in JSM 10.0.0 and below

            !image-2025-05-20-09-10-17-788.png|width=266,height=198!
            h3. Behaviour in JSM 10.1.1+

            !image-2025-05-20-09-10-32-967.png|width=381,height=276!

             
            h3. Steps to Reproduce
             # Install Jira Service Management 10.1.1
             # Configure outbound email
             # Create a Jira issue with an Asset field
             # Verify the issue created the mail notification

            h3. Expected Results

            The object label will be displayed:
            h3. Behaviour in JSM 10.0.0 and below

            !image-2025-05-20-09-10-47-992.png|width=167,height=124!

             
            h3. Actual Results

            The object key is displayed instead of the label:
            h3. Behaviour in JSM 10.1.1+

            !image-2025-05-20-09-10-57-500.png|width=251,height=182!

             
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            Rodrigo Jose Zaparoli made changes -
            Attachment New: image-2025-05-20-09-10-57-500.png [ 501712 ]
            Rodrigo Jose Zaparoli made changes -
            Attachment New: image-2025-05-20-09-10-47-992.png [ 501711 ]
            Rodrigo Jose Zaparoli made changes -
            Attachment New: image-2025-05-20-09-10-32-967.png [ 501710 ]
            Rodrigo Jose Zaparoli made changes -
            Attachment New: image-2025-05-20-09-10-17-788.png [ 501709 ]

              Unassigned Unassigned
              c3678a055509 Leonardo Souto
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: