I want anyone to be able to create jira ticket, but I don't want all of them as customers

Question

Hi

We have a situation where we have everyone within our organization created as customers when they send an e-mail to our IT support team and a ticket is created within Jira automatically.

We however also want our 3rd party cooperators to be able to send in an e-mail to our IT support team, and their request to be created as a ticket within Jira, but we do not want the sender to be created as customer in our Jira service portal. - Today only AD users within our organization can send in a Jira request.

How can we allow external parties to create a Jira request within our service portal without having them created as customers in our portal?

Best Regards

- I

Jonas Ekström · Accepted Answer

Hi Inga,

For a ticket to be created, a reporter is needed. Unless the user already exist, it needs to be created.

So for third parties to contact you they need accounts.
You can either choose to have your agents send invites, or allow for public sign-up.

This means, it's not possible to have the email channel open without accounts being created one way or another.

What's the reason you don't want them to have accounts? Maybe there is something else that can be done to remedy your concerns.

Dirk Ronsmans · Accepted Answer

Hi @Inga Gunnarsdóttir and welcome to the community!

Like @Jonas Ekström mentions, each issue requires a reporter.

If you were on server/dc you could configure your mail handler to use a default reporter which means they would be logged under that user.

Sadly on Cloud that's not possible..

I'm currently setting up a similar case myself but had to resort in using an Email app to get this functionality. For example I'm using Email this Issue (JETI) which allow me to configure the email handlers much deeper.

If you were open to investing like that (or start with a trial) you could set it up to have a specific email address set up with a default reporter.

I'm not going in to too much technical specifics yet as it would require some conversion and investment. (but that way you know there are work arounds)