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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Country of origin incoming ticket in JSM

We are working with Jira Service Management, and for reporting reasons we need to identify the country of origin of every incoming ticket, and then be able to create a dashboard with that info.


How can we solve this?



2 answers

2 votes

@Mario Tobar -

In my opinion/experience is for you to create a custom field (single select dropdown list) to populate/capture the country of origin on ticket creation.  By default in JSM, since issues can be created via email submissions and via Portal UI, it is very difficult to associate the customers country of origin to his/her account.

Hope this makes sense.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Thanks Joseph!

We can indeed create the custom field, but this info should come along with the user (informer) of the ticket in question, since we have managed account and federated domain, 


thanks again!

@Mario Tobar -

Since your customer (informer) can assist your identification of country of origin when issue is created, then you can setup Automation for Jira rule to tag your issues appropriately with the country information.  Maybe you don't even need a custom field, but just use "Labels" or other existing fields for the metadata tagging.

Best, Joseph

"Labels" is a tricky field because it is a cross-project field and case-sensitive. It can be messy after a short time.

@Mario Tobar I highly recommend you create a separate custom field to collect this data. Thanks to this, you'll be able to use it in automation, JQL, filters, and dashboards - in every place in Jira. In the future, maybe you'll be interested in using Forms and changing the form depending on the country. So try to look at this topic wider: why you need this data, how to want to use it, for whom it's collected, etc. 

Best regards,


CPO & Co-founder @Appsvio | Atlassian Community Leader 

@Mario Tobar -

I would agree with @Katarzyna Pawlak _Appsvio_ statement except if it is something simple i.e. "USA" in the labels, then it can be easily used in one or multiple projects.  

The true essentance of my suggestion besides of creating a new custom field is finding some other existing field(s) that you can use to conduct your meta data tagging.

Best, Joseph


Just a quick note to a great discussion: Labels are not case-sensitive, at least not on Jira Cloud. They can definitely be searched with JQL, updated with automation and do not have to become messy over time when used right. (And yes, I'm slightly biased pro-labels, as we have a label management app in Marketplace.)

That being said, I do with @Katarzyna Pawlak _Appsvio_ here – Labels are not the best fit for a situation where you just need one option selected from a pre-known list.   Instead, I would suggest the same solution as @Joseph Chung Yin – a single select custom field that's pre-populated with the country names.

Best regards,

0 votes

How are you detecting which country the user is in?

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events