If you are using Organizations to keep your customers organized, it's vital that the Organization gets set by default on a new ticket created in JSM.  This can be done via Automations using APIs, but I lose count as to how many JSM users in the Community request how to do this.  

This should at least be configurable and let the site administrator decide if this should be filled in or not.

We also would like to make the Department field available on our platform. The field is filled automatically by the system, but there is no Smartvalue or any other way to extract/use the information.

Hello everyone, we need this feature in 2024. It's available in the old version of automation, but not in the new version. Can you add it to the Data center too?

This would be a really handy feature to have and addresses one of our maintenance headache but I am not liking my chances given that this suggestion was created back in 2017.

Our current workaround is to set a default sharing organisation user property for each user via REST API and use automation to share it with the default sharing organisation during an automation trigger event. Unfortunately this workaround will only work if the Jira Administrator controls all/most of the user onboarding.

I guess if users can create an account by sending email in, you will have to include a process where a list of users name and account id are regularly extracted for those users without the user property and run the REST API to set the organisation value in. The Organisation name and organisation id can also be extracted to use in the script but you will have to handle edge cases where email domains like somecompany.us and somecompany.com are really the same organisation and might need to be mapped to the same organisation id like what was described in rahul's solution.

My god this isn't done yet?? Not enough money and people to make this happen? I'm sorry but this is ESSENTIAL!

I think this is essential, especially since it isn't possible right now for the organisation field to be always set (customers always have the option to "not share" with the organisation, which leaves it empty).

Any automation rules, SLA or other logic, that would be based on the organisation is then irrelevant.

+1  we have hundreds of customers, the workaround is not scalable as you say.  This is a real pain and has a tangible cost associated to it were we have people spending a certain amount of time doing this. Any chance of an update on this being changed??

+1

I am also looking for this feature.  Having many customers, each with numerous end users, all sending emails to a support alias to open tickets.  Then as the support team, we have to manually assign each issue to an organization, and it is cumbersome.

Organizations should be linked to a primary domain.  When an issue is created from any email address from that domain, it is automatically assigned to the organization.  If there is no organization already, then one is created using the domain name that the user emailed from.  The Organization's should further be able to be renamed from the domain name to the name of the business and all associated issues, or people that are assigned to the organization still remain part of the organization after the rename.

Please make this happen sooner rather than later!  Thanks!

Please, can we have an ETA on this issue? How many votes do you need this to be prioritize?