You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Пушкарь Роман ,
Currently, the only way to remove/hide this button is by removing everyone of the organization. The button only appears for customers that belongs to an organization.
We have a feature request suggesting the ability to choose a default value for the "Share with":
Please, click on vote and watch to receive updates about the feature.
For now, if the customer does not share the ticket with the organization, an agent must manually set the organization in the ticket.
I'm afraid it doesn't make any sense to set manually the Organization in a ticket if a customer decided not to share it with his Organization.
Not sharing a ticket to everyone does not mean you're not part of your Organization.
This field should really be removable.
2021 - no change. Feels like there's so many of these floating issues from Jira that are under prioritised.
This field should 100% be removable. I don't want my service desk customers sharing requests at all. I understand setting a default value, but at the same time this button should be removable. Forcing me to set a value feels immature, like you've decided what my use-case is as well as everyone else's. Give maximum usability by letting us make the decisions on how buttons like this interact.
This is all my opinion:
The Organization field is not fully thought out and it feels like JIRA is trying to solve two unique use cases with it.
1) I should be able to use the Organization field to determine what tickets belong to what Organizations.
2) A user should be able to select whether their ticket is public or private to their organization.
A customer's choice to share their ticket should have ABSOLUTELY NO relation to the Organization field. Perhaps another field should be created "Private ticket" with true or false depending on if the user wants to share or not.
So how can one field satisfy both these use cases? It makes no sense.
If one of my agents sees that Organization is blank - Is that because the customer declined to share? Or is that because our workflow failed to automatically set the Organization based on the customer's email domain? Or something else? How do I know the user doesn't want to share the ticket just because the Organization field is blank?
Because of all this, we really need fine grained control over that "Share with" field on the Portal, or a completely overhauled solution to these use cases and my suggestion is to create more fields to house the customer's decision to share or not, and then automatically populate the Organization field from their email domain.
This problem impacts downstream processes like searching for all tickets in an Organization - my search won't return results when the customer declined to share their ticket. And if I go and populate the Organization field where it is missing .... the customer may not be happy about me deciding to share their ticket. This can't be solved with one field.
This is a major issue considering it puts the power in the hands of a single customer to share their ticket with everyone in an org. Far too easy to make mistakes, or for them to do it without knowing any better, and now 100+ people in an org have access to the ticket. Aside from security issues, it's also going to confuse the heck out of people.
This field needs to have the option to be disabled, either outright or conditionally depending on the request type. There should also be the ability to update description text so users can be informed of it's function and be less prone to mistakes when it's used. Training and documentation can only go so far with that.
I really need to remove this button, my project is stuck at this point since everytime a user creates an issue and forgets to set this drop down as no one, the entire company starts to receive annoying notifications, it also goes against all our policy about privacy, security and data protection since many cases are related to internal processes. This button should never exist or be removable. Please proceed.
Hello @NUB7_8 IT Support,
Welcome to Community!
I’m not sure if you saw the ticket I shared in my first response on this thread. The feature was implemented and now it’s possible to set the default value for the field.
As a Jira administrator, go to Cog icon > Products > Configuration (under Jira Service Management).
The button will only be visible if a customer belongs to an organization. If you don’t want them to share tickets, the best option is to remove them from the Organization.
Hi @Chetan Kudalkar,
Thank you for your question!
It's not possible to hide the field, what this new feature allows is to set a default value for the field.
This is a good option, for example, if a customer forgets to check the "Share with" field, it won't be accidentally shared with the Organization.
Hi @Angélica Luz thanks for the answers here ...
We have some service desks that we want to show only to internal staff - on the portal and on the 'backend'.
We created an Org that has all the internal staff (basically a sync between a Staff group to that Org) - I have switched this option to No but the fact that the Share with field is there confuses users. And the faact that all users in the org have gotten email notifications because they in the Org
I see on https://jira.atlassian.com/browse/JSDCLOUD-4382 it is Closed but the Share with still appears on the form
Hi @Yatish Madhav,
The feature you mentioned is just to set the default behavior for new tickets created via portal or email.
It’s not possible to hide the Organization field, if a customer is a member of an org, it will appear the option for them.
Currently, there is no feature request suggesting hiding the field.
Feel free to raise one on jira.atlassian.com (project JSDCLOUD) adding more details about why this feature is important for your environment.
And the faact that all users in the org have gotten email notifications because they in the Org.
Customers on the organization received only one notification to inform them that the ticket was shared and then to receive future ones, they need to turn on the notifications directly in the ticket.
You can disable this notification directly in the project on Project settings > Customer notifications > Organization added (company-managed) or Project settings > Notifications > Customer notifications > Organization added (team-managed).
Members of the organization will have access to the ticket via portal, but they won’t be notified about that.
Thanks @Angélica Luz - I will do so. I have also created the ticket for the suggestions I have on this topic.
RE the notifications - thanks for that. I think it would be great to be able to configure this in bulk - like a notification scheme for SD projects. Right now it seems all this Customer, Organization configurations are primarily done per project not so much under the Site wide SD settings.