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; } } }

Script runner - Behavior - Limit field options based in the issue type

Humberto Gomes

Hi,

I need to show different values for same field based in the issue type.
From as I know, this can be done using Behaviors.

Jira Field:
Service and Sub-category - Is field is a cascade option.

Field options:
Service1 - 1 Sub 1
Service1 - 1 Sub 2

Service2 - 1 Sub 1
Service2 - 1 Sub 2

Service3 - 1 Sub 1
Service3 - 1 Sub 2

Context created:
Project = TESTSD
All issue types

What I need:
Issue type "Support"
must show only the options:
Service1 - 1 Sub 1
Service1 - 1 Sub 2

Service2 - 1 Sub 1
Service2 - 1 Sub 2

Issue type "BUG"
must show only the options:
Service3 - 1 Sub 1
Service3 - 1 Sub 2

Note 1 - this is to user in Service Desk

How can i do this? Can you help?

Thanks in advance

Accepted answers

Kian Stack Mumo Systems

@Humberto Gomes, can you please clarify, should this be shown on the customer portal? Or is this on the agent side?

Thanks!

Kian

All comments

Kian Stack Mumo Systems

@Humberto Gomes, can you please clarify, should this be shown on the customer portal? Or is this on the agent side?

Thanks!

Kian

Humberto Gomes

Hi,

Customer portal.

Humberto

Humberto Gomes

Customer portal view:

ScreenHunter 763.png

Issue type mapping:

ScreenHunter 764.png

Kian Stack Mumo Systems

@Humberto Gomes, I am looking into a solution!

Benz Kek _Adaptavist_

Hi there,

You can check out ScriptRunner's Library of the two below:

The idea of setting normal Select List or Cascading Select List field options are the same as given in the above links.

Other than that, do take note that there are two types of Behavior's mapping:

Project/issuetype mapping
Service Desk mapping

If you are trying to use it in Customer Portal, make sure you use the Service Desk mapping and map it to the appropriate Request Types.

Cheers~

Bill Goodall_cytj6j

Hi @Benz Kek _Adaptavist_

I find that these links you provided are done in Groovy. But we have some existing scripts written without groovy. Do i need to convert the whole script to groovy, or can i only convert this one line?

Or else can you tell me how to translate that before Groovy was being used in these scripts?

if (issueType == "Initiative" || issueType == "Feature" || issueType == "xyz Feature" || issueType == "xyz Initiative" ) {

def optionsMap = ComponentAccessor.getConstantsManager().getPriorities().findAll { priority ->

priority.getName() in ["1. Must have", "2. Should have", "3. Could have", "4. Won't have this time"]

}.collectEntries {

[(it.id): it.name]

}

formField.setFieldOptions(optionsMap)

}

Which position would we be throwing the default assignment statement into?

See my Option 1??, Option 2??, Option 3?/, Option 4?? positions below

if (issueType == "Initiative" || issueType == "Feature" || issueType == "xyz Feature" || issueType == "xyz Initiative" ) {

// Option 1??

def optionsMap = ComponentAccessor.getConstantsManager().getPriorities().findAll { priority ->

priority.getName() in ["1. Must have", "2. Should have", "3. Could have", "4. Won't have this time"]

// Option 2??

}.collectEntries {

[(it.id): it.name]

// Option 3??

}

formField.setFieldOptions(optionsMap)

// Option 4??

}

Also is this a valid approach? I am getting errors on the statement syntax

def defaultValue = optionsMap.find(it.value == "3. Could have")

[Static type checking] - Cannot find matching method java.util.Map#find(boolean). Please check if the declared type is correct and if the method exists.
Possible solutions: find(), find(groovy.lang.Closure), find(groovy.lang.Closure), min(groovy.lang.Closure), any(), findAll()

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira-service-management

jira-service-management-server