• 4,779
    • 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.

      Hide the "Share with" field from the Portal. This is not necessarily Mandatory for users. It sends annoying emails to all organization member. Please add an option to hide it as this is confusing to the users. 

       

      Workaround

      Here are some of the workaround that will help reduce the impact

      • Disable notification for “Organization added” event from Project Settings > Customer notifications
      • Disable automatic sharing of request with organization unless the customer manually selects an org at https://<YourSite>.atlassian.net/jira/settings/products/jira-service-management-configuration 
        • Set "Should new requests automatically be shared with a customer's organization?" to "No, don't share email requests with the customer's organization. Requests sent from the portal will not be shared unless the customer selects otherwise" option.

            [JSDCLOUD-10908] Hide the "Share With" Field at Customer Portal Fields

            nos added a comment -

            Absolutely, just had an email shared with our whole school environment / including staff and students.

            We need a way to disable this field somehow form the portal

            nos added a comment - Absolutely, just had an email shared with our whole school environment / including staff and students. We need a way to disable this field somehow form the portal

            Brittany Skinner added a comment - - edited

            One of our users just shared a termination form with the whole organization, almost 500 people; it is set to No one by default, but I guess they were click happy. Can't believe this is still not available after all these years and so many people requesting. 

             

            **WORKAROUND IF YOU NEED IT:

            1. For the project, go into Customer notification settings and disable the "Organization added" option.
            2. Go into the Automation for that project and set up a rule:
              1. When issue created
              2. If Organizations field is not empty
              3. Then Organizations field will be cleared

            Brittany Skinner added a comment - - edited One of our users just shared a termination form with the whole organization, almost 500 people; it is set to No one by default, but I guess they were click happy. Can't believe this is still not available after all these years and so many people requesting.    ** WORKAROUND IF YOU NEED IT: For the project, go into Customer notification settings and disable the "Organization added" option. Go into the Automation for that project and set up a rule: When issue created If Organizations field is not empty Then Organizations field will be cleared

            For external customer service desks, I want this field to not be shown to customers on the portal, but default to "share with organisation" so everyone in a given customer can see all the tickets that customer has raised. 

            At minimum, I want to default the option and also control where it is shown in the portal.

            For those of you wanting this at the top of the portal page, i found that if you move every portal field to be on a form, the portal orders it as:

            1. summary
            2. share with
            3. <form contents>

            For me, this ordering is not good as I want my customers to be focused on reporting the issue as their priority, but it may help others.

            I would want:

            1. summary
            2. <form contents>
            3. share with

            Basically - this should be a field I cam completely control and it is crazy this is not addressed.

            Oliver Moore added a comment - For external customer service desks, I want this field to not be shown to customers on the portal, but default to "share with organisation" so everyone in a given customer can see all the tickets that customer has raised.  At minimum, I want to default the option and also control where it is shown in the portal. For those of you wanting this at the top of the portal page, i found that if you move every portal field to be on a form, the portal orders it as: summary share with <form contents> For me, this ordering is not good as I want my customers to be focused on reporting the issue as their priority, but it may help others. I would want: summary <form contents> share with Basically - this should be a field I cam completely control and it is crazy this is not addressed.

            In response to 37fb3c946c7b' comment:

            "There once was a field, it's called 'Shared with'
            And people who want to get rid of it!
            But since '22, I've been down and blue
            'Cause Atlassian is not trying to fix it!
            Laa...lalala...laalaa...."

            But seriously a1217920d496 , please get this fixed. It's taking almost 4 years by now.

            FA_TESTCAD1 added a comment - In response to 37fb3c946c7b ' comment: "There once was a field, it's called 'Shared with' And people who want to get rid of it! But since '22, I've been down and blue 'Cause Atlassian is not trying to fix it! Laa...lalala...laalaa...." But seriously a1217920d496 , please get this fixed. It's taking almost 4 years by now.

            Being able to put users into organization buckets is great but why is this shown by default? I know it's a users' problem for getting easily confused by a box to click but please remove this from being shown by default.

            Kurt Anderson added a comment - Being able to put users into organization buckets is great but why is this shown by default? I know it's a users' problem for getting easily confused by a box to click but please remove this from being shown by default.

            Alex added a comment -

            Welcome a1217920d496 to our community!  We are a passionate group, united by a shared vision for a future that allows for hiding a single dropdown from the helpdesk intake form in our ticketing systems!   Or motto, often sung like a sea chanty in the gathering places across the land, is "Never doubt that a small group of thoughtful, committed citizens can persuade Atlassian to enable administrative control over the visibility of a field. Indeed, it is the only thing that ever has"

            Alex added a comment - Welcome a1217920d496 to our community!  We are a passionate group, united by a shared vision for a future that allows for hiding a single dropdown from the helpdesk intake form in our ticketing systems!   Or motto, often sung like a sea chanty in the gathering places across the land, is "Never doubt that a small group of thoughtful, committed citizens can persuade Atlassian to enable administrative control over the visibility of a field. Indeed, it is the only thing that ever has"

            We use organisation so people can search easily when they need to share a ticket with someone. But we do not want them to share with the entire org !

            We also have organisation for our internal department - this makes tickets shared with their team easier.

            So sometime we need to share with smaller organisations in our JSM. So hiding the button on creation is not helping. I'd rather have 2 options:

            • completly hide the share button
            • have it but choose with org can be seen

            Fanny Vachet added a comment - We use organisation so people can search easily when they need to share a ticket with someone. But we do not want them to share with the entire org ! We also have organisation for our internal department - this makes tickets shared with their team easier. So sometime we need to share with smaller organisations in our JSM. So hiding the button on creation is not helping. I'd rather have 2 options: completly hide the share button have it but choose with org can be seen

            Alex added a comment -

            Thinking I might just leave a comment every time I see this field (i.e. every time I file a ticket).

            Please let us hide the bad field ed36d73f045d 

            Alex added a comment - Thinking I might just leave a comment every time I see this field (i.e. every time I file a ticket). Please let us hide the bad field ed36d73f045d  

            4259cd0d93f6  if you look at the linked tickets, this issue has been going on since atleast 2018, they just keep moving the ticket and removing it from general view.  Created:18/Oct/2018 1:32 PM.. over 6 years and they couldn't be bothered to give the ability to hide this field on a form.  How hard can that be??

            Bryan McDade added a comment - 4259cd0d93f6   if you look at the linked tickets, this issue has been going on since atleast 2018, they just keep moving the ticket and removing it from general view.  Created:18/Oct/2018 1:32 PM.. over 6 years and they couldn't be bothered to give the ability to hide this field on a form.  How hard can that be??

            An ongoing issue and numerous complains from 2022. Yet here we are at the end of 2024 with no action on this. Time for us to move on to a different system it seems. Shame!

            Sabbir Quarishi added a comment - An ongoing issue and numerous complains from 2022. Yet here we are at the end of 2024 with no action on this. Time for us to move on to a different system it seems. Shame!

              a1217920d496 Ash Young
              6539e7e756cc Celine Penaredondo
              Votes:
              702 Vote for this issue
              Watchers:
              336 Start watching this issue

                Created:
                Updated: