Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,032
Community Members
 
Community Events
176
Community Groups

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

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

3 answers

2 accepted

0 votes
Answer accepted
Dirk Ronsmans Community Leader Jul 12, 2021

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)

0 votes
Answer accepted

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.

Thank you very much for your replies @Jonas Ekström and @Dirk Ronsmans 

I have another question: if we would allow everyone that send us Jira tickets to be created as customers. Could we somehow restrict them from having access to our service portal?

There is - only customers that are also AD users within our organisation would have access to our service portal but not "other" customers? (They would only be allowed to create jira tickets through our IT support e-mail)

For that purpose we created two different service desks, one for internal with extra issue types and one external with only only the email option.

Like Inga Gunnarsdóttir likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events