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

Allow JIRA Service Desk project Admin Disable Customer's ability to set organization

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Global Configuration
    • None
    • 0
    • 1
    • 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.

      Feature Summary

      Currently in JIRA, users can add organizations or request participants to their tickets. However, when a user belongs to an organization, the organization is set by default in the share option rather than private and there is no way to configure this.

      More importantly, there is no way to prevent customers from setting organizations but still be able to add Request Participants.

      Use Case

      In an company with various branches in different geolocations, if an organization is created based on the branches, when a user creates a ticket, if he does not intentionally go to select private, his ticket would be shared with everyone and when this happens to be a private ticket that should have been shared only with specific staff(say finance report or health record), the organization field would leak the information out.

      Feature Request
      1. Add a functionality that allows the JIRA Admin disable the ability for customers to share with an organization while still maintaining the ability to share with individual users.
      2. Allow the JIRA Service Desk admin specify the default for the share option.

            [JSDSERVER-5318] Allow JIRA Service Desk project Admin Disable Customer's ability to set organization

            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: 1 New: 0
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012595 ] New: JAC Suggestion Workflow 3 [ 3651170 ]

            Phillip Collins added a comment - - edited

            Is there another option?

            Could it be possible for the Jira Admin to simply stop the Notifications, that an issues has been shared with their Organization, from being sent out?

             

            Thanks

            Phillip Collins added a comment - - edited Is there another option? Could it be possible for the Jira Admin to simply stop the Notifications, that an issues has been shared with their Organization, from being sent out?   Thanks
            SET Analytics Bot made changes -
            UIS New: 1
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2663637 ] New: JAC Suggestion Workflow [ 3012595 ]

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: