• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 0
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      We have been asked if sending service desk email notifications to everyone in an organization is possible.  It appears you can only add an organization to the "Organization Added" default notification.  

      My next thought was to add the organization to the tickets "Request Participants" through an Automation script.  I quickly found that organizations are not valid.  I could create an automation script that has the members of each organization defined in it, and use that to achieve the desired result.  But it would be nice if I didn't need to keep track of the organization changes in multiple places.

       

          Form Name

            [JSDSERVER-4977] Allowed Organizations to receive notifications

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Atlassian Update – 5 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 5 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Charlie Jira Service Management, Server & Data Center
            SET Analytics Bot made changes -
            UIS Original: 3 New: 0
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS New: 2
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012489 ] New: JAC Suggestion Workflow 3 [ 3649832 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665362 ] New: JAC Suggestion Workflow [ 3012489 ]
            KellyW (Inactive) made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]
            Keri Duthie (Inactive) made changes -
            Link New: This issue is related to JSDSERVER-5816 [ JSDSERVER-5816 ]

              Unassigned Unassigned
              02217d11a32b Ben Johnson
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: