• 2,297
    • 21
    • 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.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Product update: December 20, 2024

      Hi Everyone,

      I'm sorry this has taken longer than expected but we have finalised our roadmap for H1 next year and adding custom fields ro email notifications.

      I know that this issue is a huge source of frustration for many of you so thanks for your patience.

      Supporting generic custom fields is quite a large amount of work in several parts of JSM so this will be quite a large project. 

      If I need any further input I will reach out here but in the meantime please send any input to me at bcostello@atlassian.com.

      Regards,

      Ben Costello
      Principal Product Manager, Emails 

      Issue Summary

      There is no way to add values coming from custom fields or other fields as notification variables.

      Requested Feature

      Ability to display any fields on customer notifications.

          Form Name

            [JSDCLOUD-4642] Ability To Add Custom Field Values to Customer Notifications

            Pinned comments

            Pinned by Marco Velasco

            fishern added a comment -

            not sure if this has been posted here, but I did find a quick workaround till Atlassian can make this functionality work:

            workaround: 

            You might want to consider customizing your create email notifs if that is the notification you wish to apply this too, but works great for our approval emails or anything sent out after ticket creation. 

            Hope this helps the community

            fishern added a comment - not sure if this has been posted here, but I did find a quick workaround till Atlassian can make this functionality work: workaround:  using automation, add your custom fields to your description then use the variable in your notification to post the updated description You might want to consider customizing your create email notifs if that is the notification you wish to apply this too, but works great for our approval emails or anything sent out after ticket creation.  Hope this helps the community

            We're improving the visuals on our customer- and internal-facing notifications out of Jira Service Desk, and the very limited set of variables available isn't allowing us to continue. This list should have similar support to smart variables and be able to pull in the value of custom fields in a card.
             
            For example, if I set a custom field related to a sales prospect, it then adds the sales team as a participant on the ticket and sends them an email. I want that email to include the details of this custom field(s), but the limited variables available don't permit that.

            Gerret Walczak added a comment - We're improving the visuals on our customer- and internal-facing notifications out of Jira Service Desk, and the very limited set of variables available isn't allowing us to continue. This list should have similar support to smart variables and be able to pull in the value of custom fields in a card.   For example, if I set a custom field related to a sales prospect, it then adds the sales team as a participant on the ticket and sends them an email. I want that email to include the details of this custom field(s), but the limited variables available don't permit that.

            Hi 1bbfd485bf63 

            Thanks for the update, any appreciation of ETA would be highly appreciated, we are pressured to leave notifications for automated emails if the timeline is too long. 

            For us the most important feature to solve (might be quicker to solve in the existing framework of notifications?)

            • Display ALL that the notification and request is shared with, not just the four first
            • Possibilty to display full comment history (with original request)

            Good luck with you new role!

            Karin Kennergren added a comment - Hi 1bbfd485bf63   Thanks for the update, any appreciation of ETA would be highly appreciated, we are pressured to leave notifications for automated emails if the timeline is too long.  For us the most important feature to solve (might be quicker to solve in the existing framework of notifications?) Display ALL that the notification and request is shared with, not just the four first Possibilty to display full comment history (with original request) Good luck with you new role!

            Thank you, Ben.  The most useful additions for my team would be:

            • Ability to include the full list of recipient emails
            • Access to Assets objects' names & other custom fields
            • Automation-style smart values

            Samuel Martinez added a comment - Thank you, Ben.  The most useful additions for my team would be: Ability to include the full list of recipient emails Access to Assets objects' names & other custom fields Automation-style smart values

            All comments

            Hi 1bbfd485bf63 

            I really miss the ability to add the pending reason to the customer notification when the status changes to Pending. It's frustrating for the customer not to know the reason why the ticket is pending.

            Daniel Ångefors added a comment - Hi 1bbfd485bf63   I really miss the ability to add the pending reason to the customer notification when the status changes to Pending. It's frustrating for the customer not to know the reason why the ticket is pending.

            May I suggest breaking out two parts where the information is supported and not custom fields? 

            Notifications are currently only displaying first four participants, maybe securing displaying all in the query is not as huge effort+ It has large value since companies are requesting transparency in all channels for what is shared with who. 

            The history is also in "your hands" and could hopefully be expanded with lesser effort. 

            With this said - thank you for the hard work this year - we have experience huge improvements n the solution!

            Karin Kennergren added a comment - May I suggest breaking out two parts where the information is supported and not custom fields?  Notifications are currently only displaying first four participants, maybe securing displaying all in the query is not as huge effort+ It has large value since companies are requesting transparency in all channels for what is shared with who.  The history is also in "your hands" and could hopefully be expanded with lesser effort.  With this said - thank you for the hard work this year - we have experience huge improvements n the solution!

            1bbfd485bf63 can you help me understand why the functionality from DC cannot simply be replicated in Cloud? The ${request.details} variable worked perfectly, at least for my environment of 12k users. Now that we're in Cloud, our approvers get no information on the request they've been asked to approve.

            Mathew Lederman added a comment - 1bbfd485bf63 can you help me understand why the functionality from DC cannot simply be replicated in Cloud? The ${request.details} variable worked perfectly, at least for my environment of 12k users. Now that we're in Cloud, our approvers get no information on the request they've been asked to approve.

            John Funk added a comment -

            Thank you for the update 1bbfd485bf63  - looking forward to this in the new year! 

            John Funk added a comment - Thank you for the update 1bbfd485bf63   - looking forward to this in the new year! 

            Another item being spoon fed to Atlassian for something that is available in older systems.  In looking at the last 15 suggestions released, none of them had this many votes.

            Matt Russell added a comment - Another item being spoon fed to Atlassian for something that is available in older systems.  In looking at the last 15 suggestions released, none of them had this many votes.

            1 month later and no update - what about the "I will provide another update within the week." mentioned on the 8th October?

            Everyone, not many exceptions, on every years old polls, is asking the same : Please provides some ETAs and do BETTER follow up with your customers.
            Actually, it is just unacceptable from a customer PoV imho.

            Mike Raiche added a comment - 1 month later and no update - what about the "I will provide another update within the week." mentioned on the 8th October? Everyone, not many exceptions, on every years old polls, is asking the same : Please provides some ETAs and do BETTER follow up with your customers. Actually, it is just unacceptable from a customer PoV imho.

            Dear Team,

             

            Whats the ETA for this functionality

            Siddesh Mahajan added a comment - Dear Team,   Whats the ETA for this functionality

            Evaldas added a comment - - edited

            1bbfd485bf63 , a reminder to your own commitment

            I will provide another update within the week.

            Evaldas added a comment - - edited 1bbfd485bf63 , a reminder to your own commitment I will provide another update within the week.

            It would be extremely helpful for our company to be able to add the last comment to an approval notification email. Thanks!

            Brit Hickerson added a comment - It would be extremely helpful for our company to be able to add the last comment to an approval notification email. Thanks!

            I would expect the same functionality that we have in automation rules. Smartvalues and functions should be available to create meaningful and context rich notifications.

            Dave Meredith added a comment - I would expect the same functionality that we have in automation rules. Smartvalues and functions should be available to create meaningful and context rich notifications.

              1bbfd485bf63 Ben Costello
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              1117 Vote for this issue
              Watchers:
              568 Start watching this issue

                Created:
                Updated: