I agree completely with 37a806b7cff0. Probably it's not a very business-like way to say things, and I understand that Atlassian is being overwhelmed with support tckets – but we pay you real money, and you do agree contractually to provide us real service.

While there's no SLA on feature requests, having to wait for years in case of features that would greatly simplify the work of entire departments simply makes one think of the competition.

Despite this, our only leverage and a way to express our discontent to Atlassian is the comments and the vote button – so please vote for this ticket.

I do not appreciate your candid and transparent communication.  As others have said, this is out of the box with multiple systems.  You want us to so badly use the portal for clients BUT then leave something like this out.  Explain the logic.  Are your designers fresh out of school and have no experience?  Your 'candid and transparent' response is now 3 years old and this is still open.  So, after your sales lied to us (they said it would do this but did not say that we would have to write an automation to do it) and we are rolled out, now we have to start shopping the next system having learned our lesson.

You are being spoon fed what would make this system so much better and the truly useful items sit and linger far too long.

Any updates here? Since Cloud is being rolled out now

7 years is nothing, @jakub. Most ticket only will be considered after 10-15 years.

Created 2016... c'mon. 7 YEARS?????

I recon to wait for 3 more years, to celebrate 10 year anniversary of this ticket, then wait another 5 years for integration?
Dear Atlassian, do not hesitate to raise the license cost again to implement.

This and features like this are what will likely lead us to move all of our business elsewhere from Atlassian.  This is such a basic service desk feature, I'm shocked at lack of support for it.

I have used several ticketing systems. Jira Service Desk is absolutely one of the worst for ITIL or support. I do not recommend it because of all of the things it doesn't do well or at all. I chose it only because it integrates with projects in Jira. it is the only benefit of this system and the core functionalities like domain association need to be configured with automation. This tool requires a lot of work out of the box to get to a basic support/service desk functionality.

This is a default behaviour of other email aggregator services like HubSpot - so powerful and makes a huge difference to reducing manual management of customers

We need this as well. Should be easy... @powderedtoast.com accounts get filtered into "The Powdered Toast Group" organization that I've created. 

I need this function and it's 2022. This has been on the backlog for so long. Please add this Atlassian Team. 

how is this not a feature? I create an Organization. I assign a user/email to the Organization. When that user/email creates a ticket, it should be defaulting the Organization they are in. I don't understand how this is not just a native feature.

Automation for Jira is purchased by Jira with the built in functionality... now cannot use their service, and you don't have the feature available? What gives?

please fix...

There are quite a few very basic automation features that Atlassian is "considering".

Lack of automation is the reason why agents and customers alike are pushing to move to the competition. Please wake up!

Another disappointment. Thats two strikes tonight. First found out that we cannot change a customers email address, and now this. I guess its good that I am still evaluating, although I do wish i would have know about this lack of functionality before spending so much time configuring this product. 

Wow, almost 600 votes. Still not enough obviously =(

At this point, over 4 years after this suggestion was created, I think it's safe to assume this will not become part of Jira Service Desk. From the looks of it, they have stopped paying attention to their user suggestions in general around 2014 since many of the top voted suggestions for Service Desk were created between 2014-2016. Oh well, there are other options.

This feature is highly needed....

Really need this feature... Should be a basic concept !

Kinda shocked that this basic concept isn't already built into the system actually.

We have some customers that use multiple email domains for branding purposes and this would make the automation so much more useful.  Currently we need to have an automation rule that notifies us when there is a new customer not assigned to an organization and someone needs to copy the email address and add it to the correct organization.   Not having this suggested functionality is a big miss.

this is a major blocking issue for us, and is likely to result in us having to pick a plugin; a process which in our org is slow and cumbersome. I'm stunned this isn't already a thing. 

Unable to adopt ServiceDesk due to lack of this feature

Votes dictate that something becomes considered, not that it will be implemented. There are smaller features that have been open for 8 years when I first used Atlassian.

I was super surprised that such feature is not implemented yet.. Currently we're testing JSD and are planning to use it, however to add every customer's email manually is a pain and time consuming. How many votes must be collected that feature would be added to implementation roadmap at Attlasian?

This is a basic requirement for a service desk, internal but also external clients especially. This should not have been rolled out with out it. How many years have gone by? Please incorporate this request!

Please take a look at [Tinker for JSD|https://marketplace.atlassian.com/apps/1222917/tinker-for-jsd?hosting=server&tab=overview]

Unleash your customer portal without any unnecessary barriers to entry. (Anonymous Access) by allowing your customer to access without log in and also takes care of spam by securing customer portal with reCaptcha v3.

Features:

• Public Customer Portal (Anonymous Access)
• Public portal Creation behavior
  • Auto create user by email
  • Use public user to create
• Auto add Email field to portal fields
  • (without modifying request screen)
• Limit publicly accessed Service Desk portals
• Secure Public Portal with reCAPTCHA v3
• Adding Google Analytics to Customer Portal
• Organization Association with Email & Groups
• Add Customer Portal Buttons
• Customer requests CSV exporter
• Add columns to customer request grid
• Better portal grid view

Looking forward to better Tinker Jira Service Desk to fit your needs

https://marketplace.atlassian.com/apps/1222917/tinker-for-jsd?hosting=server&tab=overview

This still remains the only reason we can't switch to the Jira Service Desk, I really wish it would be looked at...

I don't see why it is not there right from the beginning or at least importing LDAP user of certain groups into particular organizations.

This is essential for the setup at our studio, otherwise it kind of makes the whole point of organisations a bit redundant. 

We use it to allow users to be able to automatically share tickets with one another - this was recommended to me by Jira support, yet, it cannot be fully automated as we have to manually add everyone.

Please listen to your customers needs! 

We are currently evaluating Jira Cloud to be our central support solution, and this feature is the first one we looked after initial setup.

Per domain organization assignment is mandatory for B2B services provider.

Also, an API to manage those rules should be here to automatically feed Jira Service Desk per domain organization settings with CRM/ERP customer account informations.

Need this feature now please.. Jira should be able to intelligently look up the Org a Reporter is in and assign to the Org.

This is absolutely crucial.

We have been using an old Jira 6.3 with JEMH which is able to do this. (By some tricks I know, but still)

I was stunned to say the least that Jira Service Desk in 2019 cannot do this out of the box.

Come on Atlassian.

I do not want to do a lot of custom scripting to make the system do the most obvious things.

Sorry to say it, but it seems to me like you are working on a path towards the most comprehensive system out there that can do anything, except what the users really need

This would be a good addition. With a large number of new customers this can save time easily. 

It would be best if we can have this implemented. It's a great struggle.

Ya most other modern Service desk also have this. 

it is almost 3 years and still not fixed :O

If you implement this please do it as a new automation trigger (new customer) and action (assign to organization), so it can be used for many other useful things on user creation

+1 vote.  We need this flexibility, as we are providing support via JSD to 3 large companies that are competitors of each other, and the TIME it takes to allow 1 user at a time per JSD project is crippling.

If we could allow access to JSD portal by group / domain name i..e. @companyname1.com vs @company_name_2.com > this would make much more sense.

+1

P.S. How the hell this workaround with Automation works if it's adds organization to the issue field and not customer to organization...

@Ciprian

Completely agree. But if people are desperate in the mean time there is an option until it gets looked at by Atlassian (if ever).

@Reiss
Only problem this then caused for us is that everyone in an organization automatically has access to everyone elses tickets... a massive breach of security.

This should not be an issue if you modify your default permissions model and change the "Any logged in user" to something that's a bit more restrictive 

Nevertheless, we should not be using a paid third-party addon for something that should be essential functionality for a helpdesk system

@Anthony there is a work around on this but requires a paid addon; Automation for JIRA.

You can create an automation that when they log a ticket for the first time it'll put them into either an organization of your choice or automatically based on their domain. Only problem this then caused for us is that everyone in an organization automatically has access to everyone elses tickets... a massive breach of security.

So ultimately it may not even give you what you want without a huge sacrifice elsewhere

Standard feature of almost every other service desk ever used. It is a pain currently to associate new users with Organisations making the reporting of tickets related to particular organisations pretty inaccurate. On a regular basis I have to review the customers with specific domains that are not associated to an organisation, reassign them to that organisation and do a bulk edit on all the tickets they created so they are correctly associated with the organisation. Can you crack on and get this basic feature implemented please.

Actually looking at your release schedule for the past 6 months not many changes have been delivered. Can we have some reassurance that bugs/features are being actively worked on and the product has a long term future.

Yes, absolutely needed. Thanks

please implement this! 2years have past. about time to roll out

We definitely need this!!!

100 % need

This seems like a fairly obvious requirement. +1 

Any update on this? This is totally simple function, that I can't believe it's not implemented yet...

One important thought: the Customer should be assigned to an organization before creating a service request, so the request will be created with an organization assigned already.

Time flies, but still no update - do we know if this will ever be implemented?

Any idea of when this feature is gonna be available?

Are you going to sell Service Desk to Zendesk like you did with Stride? Any plans to implement new features? Let us know in advance.

I agree!

I can't beleive there is no support for this in Jira Service Desk... 

+1 - This is some basic automation that would remove a large amount of manual work.