Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-5307

Ability to choose a default setting for Organization sharing at the create issue screen.

    • 39
    • 17
    • 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.

      UPDATE: 9th October, 2020

      Hello all! I'm happy to share that we have now actively picked up this ticket and will be resolving it shortly. We will provide another update when we're done. 

      Cheers,
      Jason

      Problem Definition

      At the create issue screen, on the customer portal, the field share with is coming with the default value of an organization instead of private request, customers can accidentally share issues that must have restricted access. 

       

      Also, when a customer is part of several organizations, the default setting will be private request. In some scenarios, customers may want to have the option to select one of their organizations as their default one rather than just private.

      Suggested Solutions

      Create an option to choose the default value for the field share with at the customer portal.

            [JSDCLOUD-5307] Ability to choose a default setting for Organization sharing at the create issue screen.

            This doesn't appear to be fully resolved.
            I note that there is an option in Product Management that allows for sharing to be turned on or off by default. However...

            Let's say we want all contacts to populate the Organizations field by default.
            So Sharing would default to on and we are effectively removing the option for the contact NOT to Share.

            Is that still being reviewed?

            Rus Yates-Aylott added a comment - This doesn't appear to be fully resolved. I note that there is an option in Product Management that allows for sharing to be turned on or off by default. However... Let's say we want all contacts to populate the Organizations field by default. So Sharing would default to on and we are effectively removing the option for the contact NOT to Share. Is that still being reviewed?

            Charles added a comment -

            What or how we can hide it. We enable organization to limit visibility but we do not intend to let user share to the whole organization but more to pick user in the "Share With" drop down :S

            Charles added a comment - What or how we can hide it. We enable organization to limit visibility but we do not intend to let user share to the whole organization but more to pick user in the "Share With" drop down :S

            Fanny Vachet added a comment - - edited

            Hi,

            any news on this feature ?

            Thanks

            Fanny Vachet added a comment - - edited Hi, any news on this feature ? Thanks

            Is there any update on this implementation?

            Gilles Ijsebaert added a comment - Is there any update on this implementation?

            Hi, I am also interested in this. The whole "organization" is getting notifications from "customers" request from same organization and is being considered as spam. Brings a lot of confusion !

            Alexandra Falkiner added a comment - Hi, I am also interested in this. The whole "organization" is getting notifications from "customers" request from same organization and is being considered as spam. Brings a lot of confusion !

            Hello please add an option to deactivate the field

            Celine Penaredondo added a comment - Hello please add an option to deactivate the field

            Hi,
            How to choose default option for the setting?

             

            Grzegorz HoÅ‚ody added a comment - Hi, How to choose default option for the setting?  

            Is there a way to choose a default for customers belonging to more than one organization/groups, at the moment it is always private. It should be one specific organisation as a default. 

            Anna-Lisa Rabl added a comment - Is there a way to choose a default for customers belonging to more than one organization/groups, at the moment it is always private. It should be one specific organisation as a default. 

            How to choose default?

            Barkero Developers added a comment - How to choose default?

            Angie added a comment -

            There should be option to turn off this button as it's spamming whole organization with requests. Staff is confused.

            Angie added a comment - There should be option to turn off this button as it's spamming whole organization with requests. Staff is confused.

            There should be option to turn off this button as it's spamming whole organization with requests. Staff is confused.

            marcinwrazidlo-armadilloit added a comment - There should be option to turn off this button as it's spamming whole organization with requests. Staff is confused.

            Nir Malchy added a comment -

            How does one "Create an option to choose the default value for the field share with at the customer portal."?

            I need all my clients to share with their Organization by default. How do I do that?

            Thank you!

             

            Nir Malchy added a comment - How does one "Create an option to choose the default value for the field  share with  at the customer portal."? I need all my clients to share with their Organization by default. How do I do that? Thank you!  

            Also agreed. There needs to be a way to hide this. It's far too easy for someone who doesn't know what they're doing to choose their org, and now 100+ people have visibility to a ticket that they don't need while also confusing the heck out of them.

            This is a major issue.

            Jerrad Hermann added a comment - Also agreed. There needs to be a way to hide this. It's far too easy for someone who doesn't know what they're doing to choose their org, and now 100+ people have visibility to a ticket that they don't need while also confusing the heck out of them. This is a major issue.

            Agreed with Jenna & Kaushik. +1

            Sabbir Quarishi added a comment - Agreed with Jenna & Kaushik. +1

            I agree with the above comment. I'm still having issues with this since users will change the default to "no one" and it messes up all of the automations. Can we please have the option to disable "no one" from the drop down, or at least have a work around to this so that it always fills in the user's organization even if they share with "no one"? 

            Jenna Dobbins added a comment - I agree with the above comment. I'm still having issues with this since users will change the default to "no one" and it messes up all of the automations. Can we please have the option to disable "no one" from the drop down, or at least have a work around to this so that it always fills in the user's organization even if they share with "no one"? 

            Hi, I was wondering if there is a way to remove this option altogether so it does not appear on the create screen?

             

            Kaushik Patel added a comment - Hi, I was wondering if there is a way to remove this option altogether so it does not appear on the create screen?  

            oli added a comment -

            Hi everyone,

            I'm happy to share that this has now been implemented. Admins can change the default Organization sharing behaviour by going to Settings > Products > Configuration (under Jira Service Management), within the "Organization management" section.

            Cheers,
            Oli and the Jira Service Management team

            oli added a comment - Hi everyone, I'm happy to share that this has now been implemented. Admins can change the default Organization sharing behaviour by going to Settings > Products > Configuration (under Jira Service Management ), within the "Organization management" section. Cheers, Oli and the Jira Service Management team

            Hi,

             

            I would vote for not give the customer the option to (un)check, but always have this checked.

             

            Regards,

            Jaap

            Jaap van Driel added a comment - Hi,   I would vote for not give the customer the option to (un)check, but always have this checked.   Regards, Jaap

            Muhammad added a comment -

            Hi Jason D Cruz, 

            Good to hear that you are working on a solution. 
            But we actually need this to default to the current users org. As our clients want's the tickets to be shared with others in their org. But this is not working for us. 

            When they open the form it shows Share with "their org" but when submitted, it's not under share with any more. Also the Organisation field doesn't get filled in. 

            If this is a known issue, can you please guide me to any article to resolve this? 

             

            Regards,

            Muhammad.

            Muhammad added a comment - Hi Jason D Cruz,  Good to hear that you are working on a solution.  But we actually need this to default to the current users org. As our clients want's the tickets to be shared with others in their org. But this is not working for us.  When they open the form it shows Share with "their org" but when submitted, it's not under share with any more. Also the Organisation field doesn't get filled in.  If this is a known issue, can you please guide me to any article to resolve this?    Regards, Muhammad.

            John Price added a comment -

            Thank you!

            John Price added a comment - Thank you!

            Hello all! I'm happy to share that we have now actively picked up this ticket and will be resolving it shortly. We will provide another update when we're done. 

            Cheers,
            Jason

             

            Jason D'Cruz added a comment - Hello all! I'm happy to share that we have now actively picked up this ticket and will be resolving it shortly. We will provide another update when we're done.  Cheers, Jason  

            +1 Our organization still needs this to be done.

            Thomas Corkran added a comment - +1 Our organization still needs this to be done.

            Come on guys.. give them a break, the ticket has only been open 3 and a half years.

            Someone must have broken the SLAs on this project. lol

            Bevan Mills added a comment - Come on guys.. give them a break, the ticket has only been open 3 and a half years. Someone must have broken the SLAs on this project. lol

            Major issue for us down stream if a customer opts not to share. Our preference is to allow this to be hidden on the form.

            Deleted Account (Inactive) added a comment - Major issue for us down stream if a customer opts not to share. Our preference is to allow this to be hidden on the form.

            Amy Fong added a comment -

            I agree a default to private is better than a default to share with the organization.  

            Even removing this field would be an idea because there is a 'request participants' field where we can add certain people, not everyone in the organization

            Amy Fong added a comment - I agree a default to private is better than a default to share with the organization.   Even removing this field would be an idea because there is a 'request participants' field where we can add certain people, not everyone in the organization

            Recently, We had some widespread incidents in connection this issue. Really need the solution of this problem.

            Tibor Gulyás added a comment - Recently, We had some widespread incidents in connection this issue. Really need the solution of this problem.

            Still waiting here as well. As configurable as your product is, I'm truly shocked that this tiny problem is still affecting admins.

            Justin Torrence added a comment - Still waiting here as well. As configurable as your product is, I'm truly shocked that this tiny problem is still affecting admins.

            eihoward added a comment -

            Still waiting.

            eihoward added a comment - Still waiting.

            Nir Malchy added a comment -

            The default is what should be configured. If I could, I'd configure the default to be sharing with the organization, since that populates the organization in the Jira ticket, which is important to our tickets analysis. 

             

            Nir Malchy added a comment - The default is what should be configured. If I could, I'd configure the default to be sharing with the organization, since that populates the organization in the Jira ticket, which is important to our tickets analysis.   

            Still looking for this feature. It should default to no one or at the very least be configurable.

            Michael Karr added a comment - Still looking for this feature. It should default to no one or at the very least be configurable.

            John Price added a comment -

            This is a mess.  We just added our employees to an Org to simplify creating private Service Desks at the suggestion of Atlassian.  Right after that:

            1) The first users accepted the default Share With Org and sent emails to thousands of people.

            2) I figured out how to disable the notification for this, which I think should be off by default.

            3) But there's still no way to avoid every submitter having to explicitly opt out of sharing their personal ticket with a large org.  This is not realistic.  

            I think 99% of the time, users will want to either not share, or share with a specific person.  In any org bigger than 5 people, why would you even want to share with the entire org?  

            Please change the default and/or let us take this off the initial submit form.  There should also be helptext/cue to let people know the ramifications of sharing.

             

            See also https://jira.atlassian.com/browse/JSDCLOUD-4382.

            John Price added a comment - This is a mess.  We just added our employees to an Org to simplify creating private Service Desks at the suggestion of Atlassian.  Right after that: 1) The first users accepted the default Share With Org and sent emails to thousands of people. 2) I figured out how to disable the notification for this, which I think should be off by default. 3) But there's still no way to avoid every submitter having to explicitly opt out of sharing their personal ticket with a large org.  This is not realistic.   I think 99% of the time, users will want to either not share, or share with a specific person.  In any org bigger than 5 people, why would you even want to share with the entire org?   Please change the default and/or let us take this off the initial submit form.  There should also be helptext/cue to let people know the ramifications of sharing.   See also  https://jira.atlassian.com/browse/JSDCLOUD-4382 .

            This is a very serious security concern. Organizations are completely unusable for an Internal Help Desk with this limitation (employee termination is a perfect example). Also, we would like to use Organizations for external customers, but similar privacy concerns for tickets from our customers prevent its use. Defaulting the value to "Share with Organization" is even more disturbing as it almost ensures that an unwanted share happens by a customer. These should be core use cases for Service Desk/Organizations and IMHO the design choices here feel very bizarre.

            Jason Hiller added a comment - This is a very serious security concern. Organizations are completely unusable for an Internal Help Desk with this limitation (employee termination is a perfect example). Also, we would like to use Organizations for external customers, but similar privacy concerns for tickets from our customers prevent its use. Defaulting the value to "Share with Organization" is even more disturbing as it almost ensures that an unwanted share happens by a customer. These should be core use cases for Service Desk/Organizations and IMHO the design choices here feel very bizarre.

            Uttaran added a comment -

            Default to share with entire organization is bothersome.

            Uttaran added a comment - Default to share with entire organization is bothersome.

            we're trying to promote Jira service desk cloud for customers. but today i came across this problem. Is it possible that this field cannot be removed from the service request?

            Consulente Atlassian added a comment - we're trying to promote Jira service desk cloud for customers. but today i came across this problem. Is it possible that this field cannot be removed from the service request?

            This seriously needs to be removed, it only confuses our customers and I find no other options than to not use organizations.

            Keven Perreault added a comment - This seriously needs to be removed, it only confuses our customers and I find no other options than to not use organizations.

            We don't want this option to be available to our customers rather configure it ourselves so that make sure necessary information is shared organisation wide. At the moment we are not able to disable this feature.

            Balpreet Wairar added a comment - We don't want this option to be available to our customers rather configure it ourselves so that make sure necessary information is shared organisation wide. At the moment we are not able to disable this feature.

            Please remove this useless option.

            Thanks.

            Javier Garay added a comment - Please remove this useless option. Thanks.

            This is very important. We service organizations that require clarity for all the reporters.

             

            A lot of them are associated with multiple organizations, but they should share the message with at let one of them. The default is 'No Share' is a bug disruption since the reporters forget to share, and we end up spending time going into the tickets and updating organizations, not to mention explaining why our clients cannot see the tickets others submit for the same organization. 

            We definitely need to configure this (In my case, remove the "No One" option or set it as NOT the default).

             

             

            Nir Malchy added a comment - This is very important. We service organizations that require clarity for all the reporters.   A lot of them are associated with multiple organizations, but they should share the message with at let one of them. The default is 'No Share' is a bug disruption since the reporters forget to share, and we end up spending time going into the tickets and updating organizations, not to mention explaining why our clients cannot see the tickets others submit for the same organization.  We definitely need to configure this (In my case, remove the "No One" option or set it as NOT the default).    

            +1 from me. Not having a default org is causing us issues when team members have raised requests then go on vacation without sharing with their colleagues & we're having to add orgs retrospectively on a case-by-case basis.

            Karyn Tooke added a comment - +1 from me. Not having a default org is causing us issues when team members have raised requests then go on vacation without sharing with their colleagues & we're having to add orgs retrospectively on a case-by-case basis.

            As a workaround, I tried to define a custom automation rule to set the 'Organizations' field to a default value upon issue creation, but unfortunately 'Organizations' is not available in the drop-down menu:

            Azadeh Maghsoodi added a comment - As a workaround, I tried to define a custom automation rule to set the 'Organizations' field to a default value upon issue creation, but unfortunately 'Organizations' is not available in the drop-down menu:

            eihoward added a comment -

            Any changes to this issue yet?

            I need to hide the field or change the default to private.

             

            eihoward added a comment - Any changes to this issue yet? I need to hide the field or change the default to private.  

            Agree with Harel. This should be configurable. You should be able to select a default if you want for sharing. There should also be the ability to turn off being able to edit the sharing. We have the issue where portal users are selecting to not share but we need the organization to be tracked. 

            Danielle Mather added a comment - Agree with Harel. This should be configurable. You should be able to select a default if you want for sharing. There should also be the ability to turn off being able to edit the sharing. We have the issue where portal users are selecting to not share but we need the organization to be tracked. 

            We use this feature to automatically share tickets between customers.

            Please don't disable it completely or default it to off - if a change is made please add a project configuration to control default sharing.

             

            Harel Safra added a comment - We use this feature to automatically share tickets between customers. Please don't disable it completely or default it to off - if a change is made please add a project configuration to control default sharing.  

            I would suggest the default should be Private and give other options in drop down

            Ravi Shankara added a comment - I would suggest the default should be Private and give other options in drop down

            This is a serious hindrance!

            Jhankar Ranjan Patel added a comment - This is a serious hindrance!

            Seriously? I have to make to identical organizations to get the default to be private? That's crazy. Please fix this!

            Terry Welliver added a comment - Seriously? I have to make to identical organizations to get the default to be private? That's crazy. Please fix this!

            Hi,

            Ah ok, this is too generic, we have some customer that have 35 users.

            We really need a standard option to be a select "participant list" which only sends emails to the reporter and the participants

            Paul Pulham added a comment - Hi, Ah ok, this is too generic, we have some customer that have 35 users. We really need a standard option to be a select "participant list" which only sends emails to the reporter and the participants

            Hello paul1766401385,

            The default notification settings are to send notifications to all participants involved in the ticket. All customers in the organization are the participants because the ticket is shared with the organization. If you would like to send the notification to Reporter only, for example, this can be done:

            1. Go to Project Settings > Customer notifications
            2. Edit the notification rules
            3. Under To field
              • Remove Customers involved
              • Add Reporter (customer)

            Note that this will cause all participants not receiving any notification, even they are not in the organization but added separately.

            Here you can find further documentation to support:

            Best regards,
            Gabriel

            Gabriel Muller (Inactive) added a comment - Hello paul1766401385 , The default notification settings are to send notifications to all participants involved in the ticket. All customers in the organization are the participants because the ticket is shared with the organization. If you would like to send the notification to Reporter only, for example, this can be done: Go to Project Settings > Customer notifications Edit the notification rules Under To field Remove Customers involved Add Reporter (customer) Note that this will cause all participants not receiving any notification, even they are not in the organization but added separately. Here you can find further documentation to support: Managing service desk notifications Customize the notifications you send to your customers Best regards, Gabriel

            We would like this.

            Also a way that doesn't send an email out to everyone in the organisation. "Share w/o email"

            Paul Pulham added a comment - We would like this. Also a way that doesn't send an email out to everyone in the organisation. "Share w/o email"

              owessels oli
              aschneider@atlassian.com Adalberto Schneider
              Votes:
              227 Vote for this issue
              Watchers:
              157 Start watching this issue

                Created:
                Updated:
                Resolved: