nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to make new issue in Service Desk default to private (do not share with organization)

Sławomir Mikuła

New feature was added in JIRA Service Desk to group people by organizations. By default customer from that organization create issue with share set to that organization. From manual: "If a customer is in an organization, they can also share the request when they raise it. By default, the request is shared with the customer's organization unless they select Private".

In this state the issue is shared between all of the participants in the organization which causes email notification to all parties involved e.g. mail to 100 people from which only 3 is interested in.

We would like to keep grouping customers by organizations for reporting purposes.

How can I set the default rule to private or even disable this combobox from raise request portal page ?

TL;DR: I do not want to share issue and notify by email warning all organization members. I want to select participants manually from issue page.

Accepted answers

All comments

Jack Brickey_h10pa4

I too am interested in this. I have been looking for similar solution. Here is a thread that I submitted that involved Atlassian rep. https://answers.atlassian.com/questions/43207726

Jack Brickey_h10pa4

Well....if I would have only read the latest response from Atlassian on my KB inquiry I could have answered this right off.

To disable notifying all customers in an organization each time an issue is created go to Project>Project Settings> Customer Notifications and disable the "Organization added" notification.

Sławomir Mikuła

ok, thanks for a tip. I was looking at that notification but thought that this is only triggered when new organization is added to the customer list. I'll check it.

Stephen Gordon_viojkx

AHHH! perfect! That totally just saved me so many headaches!

Brad Mace [ATS]

One thing I noticed is that if the user belongs to more than one organization it will default to private

Anthony France

Yeah, but the issue is then still shared with everyone in the org so they could potentially leak sensitive information such as employee terminations and what not. The notification as just been disabled.

unknown

Is there any way to keep the notification and default all requests to private unless the user specifically wants to notify their org?

Kel Hill

I would also like to know if it is possible to make the default Private and only share by choice, without having to disable sharing entirely.

Rachael Bumb

I agree. Having the ability to have "Private" be the default would be VERY helpful

Susan Ostreicher

Hi everyone. I was researching the same issue, and came across this conversation as well as a reported issue: JSDCLOUD-4382. If you're frustrated by this too, please head over and vote for it.

nprasad

I see this as a huge Bug in the system. It does not make sense at all the way it is setup right now. 90% of service tickets do not need to be shared with the whole organization and thus organizations should not be added by default. Why does the whole organization need to know when printer toner needs to be ordered! Needs to be set private by default or not shown to the customer at all. The Administrator should decide whether the customer should be allowed to share the particular Request type as it is done with Request Type forms.

I saw one workaround posted where you need to create multiple Organizations and put all users in at least 2 organizations. that way it defaults to Private. This workaround just puts more work on the administrator to manually manage the system. Personally, now I have to manually add 500 customers to 2 organizations... and thats just one of our Client Silo's. In addition, now I have to keep up with additions and removals of customers to make sure they are added and removed from both organizations instead of just letting customers sign up in their respective customer portals.

The second workaround is to disable the Automation where it sends the email when organizations are added. Why? I like this feature and helps us manage incidents where our agents can add an organization group that holds client stakeholders, and they get notified and can opt in to follow the ticket. I believe, this is what it is designed for and a critical feature for us. Thus, this workaround is not acceptable either, as it makes the whole "Organizations" feature useless.

I have been a JIRA Software fan for over 5 years and pushed my company to use JSD. I hope Atlassian fixes this quickly as now I am struggling to accomodate some basic requests from my company.

Dieter

Hi all,

I quickly rushed through all the given answers now but haven't found yet the following work-around that uses JIRA core built-in funcionality.

I thought it might still be helpful for some of you so here it is:

I have figured out that an issue is not shared to any organization member when the custom field "Organizations" is cleared. One can clear this field automatically when the issue is created using a built-in workflow post function.

Just add the marked post function to the Create transition of the workflow. It must be before "Create the issue originally"

You can find more about editing the Create transition (or initial transition) here

Thanks to JIRAs powerful workflow schemes you can use the modified workflow for the sensitive and private issue types and the default one for the public issue types like Suggestions, Improvements, Reproducible Bugs, ...

I must admit i have not yet tested if this work-around also prevents notifications from being sent to other organization members but even though it does removing the customer notification rule helps you.

Despite of all the given workarounds including my own i agree with the overall opinion here that the default sharing mode for each new issue must be private. I can't understand why Atlassian hasn't fixed this yet. To me this is a security bug not a suggestion or a new feature.

Regards,

Dieter

David Blundell

Hi Dieter,

I have tried to add a post function to the Transition: Create as you did.

On the "Add Post Function To Transition" page I have chosen "Update Issue Field"

This gives me a page with several options. I assume that you chose the "Update Issue Field"

I then get to choose what to set the value of - I can't see Organization in this list.

Please will you let me know which option you chose to clear the Organization field in the post function?

Thanks in advance for your advice,

David

Sam Hall_h1otcf

From the screen shots, I think that it might be the "Clear Field Value" post function.

I think this post function is natvely available in JIRA Cloud, but not JIRA Server (which I think is what you have David?).

The history is: JIRA Cloud used to come bundled with the Suite Utlities for JIRA (JSU) add-on, which included a "Clear Field Value" post-function.

Atlassian removed JSU around May 2017, but implemented native versions of much of the JSU stuff in JIRA Cloud - including the "Clear Field Value" post-function - so that those of us who were relying on the bundled functionality wouldn't lose out.

Read about that in Dave Meyer's post here:

https://community.atlassian.com/t5/JIRA-Core-questions/Why-is-JIRA-Suite-Utilities-disabled-on-JIRA-Cloud/qaq-p/368253#M30095

So I think the upshot is (for some instances at least) JIRA Cloud has more built-in post-functions than JIRA Server.

That might explain the difference.

Dieter

Thank's Sam for your clarifications.

So @David Blundell, are you on JIRA Cloud and don't have the "Clear field value" post function?

If yes you should contact Atlassian Support to enable that for you. If no just install the JSU plugin which is a must on each JIRA server though ;-)

Abby Welbourn

this has been a workaround for this issue for me- when I add a new customer, I add them to two organizations (just duplicate lists) and the requests default to 'private'

Micha Brans

Just voted there, however mostly it doesn't matter how many votes a requests has, Atlassian just does the changes they can fix easy, without looking at customers needs, unfortunately.

Mayssam Ismail

Yes this is a must have

Saskia Zeedijk

For Jira Service Desk Server this has been fixed now (from version 4.7.0); issue: https://jira.atlassian.com/browse/JSDSERVER-4382. Not solved for Cloud yet.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-desk

jira-service-desk-cloud