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

Select List Conversion filtering


Hello dear@Thanos Batagiannis [Adaptavist]  , @Daniel Yelamos [Adaptavist], @Roland Holban (Adaptavist)

I've encountered problem with select list conversion.  Results in list highlighted but not filtered. 

As i can see screenshots in this instruction (which i followed), result should be filtered, but it is not.


Here is the code of rest endpoint:

import com.atlassian.jira.web.bean.PagerFilter
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.jql.parser.JqlQueryParser
import groovy.json.JsonBuilder
import groovy.transform.BaseScript
import ru.raiffeisen.main.helpers.ConstantsHelper


@BaseScript CustomEndpointDelegate delegate

getTemplates(httpMethod: "GET") { MultivaluedMap queryParams ->
def query = queryParams.getFirst("query") as String
def user = ComponentAccessor.jiraAuthenticationContext.getLoggedInUser()
def rt = [:]
def jqlQuery = "project = \"TEST\" and status = In Progress"
def issueManager = ComponentAccessor.issueManager
def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser.class)
def searchProvider = ComponentAccessor.getComponent(SearchProvider.class)

def query1 = jqlQueryParser.parseQuery(jqlQuery)
def results =, user, PagerFilter.unlimitedFilter)
def customField = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectsByName("text custom field").first()
def templateList = results.issues.collect { issue-> issueManager.getIssueObject( }.findAll {it != null}
rt = [
items : templateList.collect { String row ->
value: row,
html: row.replaceAll(/(?i)$query/) { "<b>${it}</b>" },
label: row,
total: templateList.size(),
footer: "Choose template... "
return Response.ok(new JsonBuilder(rt).toString()).build();


And behaviour:

ajaxOptions: [
url : getBaseUrl() + "/rest/scriptrunner/latest/custom/getTemplates",
query : true, // keep going back to the sever for each keystroke
// this information is passed to the server with each keystroke
formatResponse: "general"


May be I am missing something common?

I ve tested it on Jira v7.2.15 and Scriptrunner versions: 5.2.2, 5.4.28

and Jira v7.8.1, SR v5.4.28

Thanks in advance!


4 answers

1 accepted

1 vote
Answer accepted

Hi Mark, 

You will need to do the filtering in your rest end point. 

So, for a case insensitive search, you will need something like 

def templateList = results.issues.collect { issue-> issueManager.getIssueObject( }.findAll {it != null} as List<String>

rt = [
items : templateList?.findAll { it.toLowerCase().contains(query?.toLowerCase())}?.collect { row ->

// rest of the script

That should do the trick, ping me if it doesn't :)

Kind regards, 


Many thanks, @Thanos Batagiannis [Adaptavist]!

It works perfect!

As i noticed, for all time that i work with scriptrunner plugin, many useful things just not described in documentation, like this for example or for setFormValue have examples only for selectlists and textfields and for dates, userpickers, grouppickers need some R&D actions from users.

In my opinion behaviours very poorly documented, I am using Idea and see so many methods in behaviour api, which are not described. It will be great to do JavaDoc for them.

So i have one question.

Do Adapatavist have plans on improving documentation?

Hi Mark,

Glad that we made it work.

I hear you and you are right. The thing is that ScriptRunner abilities are endless and no kind of 'traditional' documentation can cover all the cases. 

So right now we are working into 2 major areas 

The first one is to improve our "traditional" documentation - in progress

The second one is a way to share scripts with the public in a better way than just examples in the documentation - in progress

Regarding the select list conversion issue itself, we are also working in a solution that will make it much more easier and more flexible. 


Kind regards and thanks a lot for the feedback,


@Thanos Batagiannis [Adaptavist]  , I have the same issue as @Mark Markov , but with diferent porpose as well as diferent code, isn't for a issue but for a request.  

Could you help me also? 



Hello @Mark Markov  and @Thanos Batagiannis [Adaptavist] 

I need to implement something like this:

I want to create a select list field for a particular project with options which appear on screen as:

<value of a custom field(any other custom field) of an issue><space><Value of summary field of the same issue>

 and the no. of options should be same as the no. of issues in that particular project.

Could you please help.

Thanks and Regards,

Swapnil Srivastav.

I have problem on setting default value on user picker on customer portal. I think I need this one. can you help? @Mark Markov

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events