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,463,076
Community Members
 
Community Events
176
Community Groups

Is it possible to search for organizations using organization name?

Hello everyone,

Objective: When client submits a jira ticket, I would like to extract their organization ID from the organization name field in the jira ticket through an automation rule.

I have been following https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-organization/#api-rest-servicedeskapi-organization-get this tutorial and was able to extract a collection of ALL organizations (and their associated ID's), however there does not appear to be a way to actually query based on the organization name.

Does anyone know of any way I could extract the organization ID based on the organization name in an automation rule?

Thank you very much

2 answers

1 accepted

2 votes
Answer accepted
Mark Segall Community Leader Mar 29, 2022

Hi @tom_daudelin - It is possible to capture the Organization ID and Name with a smart value.  Organization is simply another custom field so you need the ID and then this is how you would capture the name and ID respectively:

{{issue.customfield_xxxxx.first.name}}
{{issue.customfield_xxxxx.id}}

Hello Mark, but this solution would require either the client to know their internal Jira ID or it would require us on our end to know their IDs.
This is not optimal for us.
For one: This leaves us open to human error in a context of highly sensitive data (i.e should we accidentally input the wrong ID, we could be exposing data to the wrong organization).
For two, we do not know the organization's IDs to begin with. Furthermore, we cannot locally store any of these Organization:ID key value pairs given that at any point an organization we work with can change their name. And when managing an evironment with hundreds of organizations, that is a recepie for disaster.
Finally, it would be best to leverage what is already being stored by jira through : 'https://your-domain.atlassian.net/rest/servicedeskapi/organization' rather than copy it as a static table on our end.

We would like to pull the ID at runtime or find a way to store the ID's locally in a way that is scallable and dynamic.

Thank you!

Mark Segall Community Leader Mar 29, 2022

I think it would help to take a step back and better understand what exactly you're trying to accomplish.  I interpreted that you wanted to establish automation rules but were unable to capture the Org ID.  Based upon that premise, the organization is captured as the customer generates a request and that value is stored on the organization field with the issue.  So, if you're trying to get the organization ID from a specific issue for the purposes of automation, you can get it as I shared in my last post.

If this is not the intent, please share a bit more about the process you're trying to automate (how you want it triggered, desired action(s) to occur, conditions, etc.).  

Ahhhhh, I understand now!
Thank you so much for the help.
In automation, {{organizations.id}} returns the organizations id as desired.
Thank you so much for the help!!

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events