nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to find all the Option ID's for the Customer Request Types

PhilSpo

Hello,

Im looking to add in some Workflow Transition Conditions so that agents can only move tickets raised with a particular Customer Request Type to a particular Status.

I have figured out already by reading articles in the Atlassian Community that this will only work if you set the Comparison Type to 'Option ID' 'See Screenshot'

The only thing i cant work out is how to get a list of all the Request Types and their corresponding ID's.

Is there a way of doing this using API?

Cheers

Phil

Accepted answers

All comments

Callum Carlile _Automation Consultants_

@PhilSpo If you go to your Project Settings > Request Types then click on Edit Fields for each request type, there will be a number right at the end of the URL, this is the ID for that request type.

Alternatively, you can enter:

"https://your-domain.atlassian.net/rest/api/3/issue/DEMO-1" (where DEMO-1 is the key of a Jira issue in your instance which has a request type associated with it)

By then doing a Cntrl+F if you search for requesttype it will reveal the ID of the request type used for this Jira issue (in example below, the ID of my request type is 53). You would have to repeat this for other tasks of other request types, so I think the first method would be much quicker

Hope this helps!

PhilSpo

Hello,

I managed to work it out:

https://your-domain.atlassian.net/rest/servicedesk/1/servicedesk/request/10071/request-types

brings back all the relevant request types for that issue type:

avatarType=SD_REQTYPE&avatarId=10508","issueType":10011,"issueTypeIconUrl":"/secure/viewavatar?size=medium&avatarId=10558&avatarType=issuetype","createScreenId":0,"viewScreenId":0,"issueTypeName":"Support","name":"Urgent Out of Hours Voicemail","description":"Out of hours urgent voicemail received","descriptionHtml":"<p>Out of hours urgent voicemail received</p>","helpText":"","helpTextHtml":"","order":0,"usedByEmailSettings":false,"groups":[],"practices":[]},{"id":42,"cvId":5,"portalKey":"ccs","portalId":5,"key":"1ea9d869-77e8-4576-ae55-ae6fdfed451e","icon":10493,"iconUrl"

I have underlined and bold the key that is the option ID

Phil

Callum Carlile _Automation Consultants_

@PhilSpo Have you tried using this ID in your workflow condition? In the section you highlighted, I would have thought the request ID is this:

{"id":42,"cvId":5,"portalKey":"ccs","portalId":5,"key":"1ea9d869-77e8-4576-ae55-ae6fdfed451e","icon":10493,"iconUrl"

I could be wrong though, so apologies if I am!

PhilSpo

Hey @Callum Carlile _Automation Consultants_ Yes I tried it and it works.

However I found out that the OptionID is made up of two separate parts concatenated together: portalKey/key

So from the above example I used 'ccs/1ea9d869-77e8-4576-ae55-ae6fdfed451e'

As you can see below, its not very intuitive for yourself or anyone else to know what's going on if they ever need to edit the transition conditions. I will have to make a note of which key is which request type.

Cheers

Phil

Ignas Selvestravičius_b13wvr

Thank you guys, it worked for me too:

First, you have to get issue id through REST
```
https://[instance].atlassian.net/rest/api/3/issue/[issue key] 
```
where '[issue key]' is your issue key (XYZ-1) and '[instance]' is your instance name.

Then you have to get portal key and request key

https://[instance].atlassian.net/rest/servicedesk/1/servicedesk/request/[issue id]/request-types

Note: Issue id is not issue key.
request key.jpg

In the Condition you choose Value field, compare with option ID, in the value you add
```
[portal key]/[request type key] 
```
You will het something like "inosup/bas124653dfsd...." you get the idea

Thats it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud

atl-gruland