Organization field not populating for some client emails

[Matt Miller]

Some client emails aren't populating the "Organization" field on new issues. Note: This is not for portal submissions, but specifically email. We use the Organization field to auto-assign new issues. We have an internal user with an external client's email for testing, and their emails don't populate the Organization field even though that email is listed as a customer in the organization field. However, some clients that email in do get properly assigned to an organization. 

Is there some sort of weird API interaction between the MX endpoints of some users and Atlassian that is setting the "do not share" flag (similar to in the portal) and preventing an organization being assigned to the issue for some users rather than others? 

Alternatively, anyone know how I can have automation check if the reporter is a member of an organization and then manually set the organization via JQL? Something like:

IF reporter IN organizationMembers("KPMG") SET issue.organization("KPMG");?

Thanks!

[Fernando Eugênio da Silva]

@Matt Miller , Welcome to the Atlassian Community!

Even I'm not understanding completly what you are trying to do, I should say that you can use User Condition in an automation rule to check if the user is a participant of specific Organization. Check the print details:

If this condition don't work for you, could share more specific details about your issue, please?

Thanks,

Fernando

[Matt Miller]

Unfortunately I tried this and it doesn't work. Sometimes it doesn't register that the customer is in the organization, and it never puts the organization in the "organization" field of the issue.

[Fernando Eugênio da Silva]

Got it!

Well, in this case as is working for some customers and the issue it seems more specific. I suggest you to try contact Atlassian Support team: https://support.atlassian.com/contact/#/

They can take a look if there's some safety rules or something else blocking the action