You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
When creating a ticket from the portal, the 'Organizations' is updated automatically according to the values that are defined in the 'Customers'.
A few internal teams create tickets directly from jira, but when they do so, the 'Organizations' field is not updated.
I saw that there is a template in the automation named "Set organization using reporter's email domain", but it does not answer my need. For some reason, it does not update the existing Org and it adds every user to a specific Org value.
Can you please share a solution that will fit my needs?
Are your internal team agents raising issues on behalf of the Organizations?
Could you not make the 'Organizations' fields as required on the create transition?
Our customers are internal teams in the company. Only some of them have Jira.
The 'Customers' field contains those teams (we manage it manually every time a new employee is added to the company).
In order for us to understand who raised a ticket (from which team), we use the Organization field
I assume they are raising issues in Jira?
Is the Portal an option for you?
From my experience on a Data Centre deployment:
If a customer is associated with only one Organisation, then it can be automatically populated if the configuration is set. If the customer emails an issue in, then the same will apply. Gets more troublesome if a user is associated with more than one.
If users are raising issues from with Jira, then you can either make the Organizations field mandatory or use some form of automation to populate it.
The issue is that we have several organizations (per team), but the domain of all the users (employees in our company)
For some reason, when they tried to open a ticket from Jira and not the portal, and when I used the automation that I described above, it did not update the relevant organization and added them to a specific value - all of them.
I need a solution that will give me the same results as the portal gives
Hi @Orly Dahan
The way issues are raised differ between the Portal and Jira.
I would suggest looking into some automation to look up the Organization that the user is associated with and then populate the field, if making it mandatory isn't an option.