Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

LDAP User Picker (ScriptRunner) error.

Tony Montana
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 24, 2026

I created LDAP User Picker. Added it to Screen and try created issue.

We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.

When picker is loaded. if picker is cleared issue created fine. But then if issue Edit so infinity loaded edit screen. Nuff Said.

Settings
All instance on UTF-8
Field
Search attribute
msDS-PhoneticDisplayName

Display attribute
msDS-PhoneticDisplayName


In preview all works.изображение.png

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
Marc -Devoteam-
Community Champion
March 24, 2026

Hi @Tony Montana 

Did you asked your admin for log filer, as you run DC (on-prem) contact them.

Also has a resource for the user been created?

See documentation; https://docs.adaptavist.com/sr4js/latest/features/script-fields/built-in-script-fields/ldap-picker 

Tony Montana
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 25, 2026

Are you kidding or don't you see the preview screenshot?

Marc -Devoteam-
Community Champion
March 25, 2026

Hi @Tony Montana 

I see you screenshot, but did you look at log files on the server(s) for information.

What are messages in there?

Even if you would ask this directly to scriptrunner support, they need information for the log files.

No I'm not kidding!

Tony Montana
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 25, 2026

@Marc -Devoteam- When I disabled ScriptRunner as plugin so I can reindex and my  "blocked" issues are apeare. And when I enabled ScriptRunner LDAP Pickers also apeeares in this issues. And works fine (I can edit it). But created error anyway still. If I run reindex when ScriptRunner is enable I see in log file 

JiraTaskExecutionThread-4 INFO [c.a.j.issue.index.IndexingStatsManager] [indexing-stats] Resetting stats.
JiraTaskExecutionThread-4 INFO [c.a.j.issue.index.IndexManagerBase] Reindexing 38640 issues in the background.
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79113'
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79111'
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]
2JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79109'
iraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79108'
 JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]
JiraTaskExecutionThread-4 WARN  [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79106'
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79105'
JiraTaskExecutionThread-4 WARN [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]


Guess... This error could be after Created-Removed test tasks with LDAP Picker... On this JIRA 11 all works trough the ass...

Marc -Devoteam-
Community Champion
March 25, 2026

Hi @Tony Montana 

On the local server where Jira is running, check the Atlassian log file what is happeing on when you are executing the action.

As the provided details, only relate to the index, not when the scriptrunner actions is done.

Is customfield_12200, the scripted field you use for the LDAP user picker>

Tony Montana
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 25, 2026

Yes it is

Tony Montana
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 25, 2026

Here is full log after click button Create

2026-03-25 22:24:40,525+0200 http-nio-8080-exec-21 url: /secure/CreateIssueDetails.jspa; user: mazafaka WARN mazafaka 1344x1086x1 587yrj 192.168.216.18,127.0.0.1 /secure/CreateIssueDetails.jspa [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Entity - '79200'

2026-03-25 22:24:40,525+0200 http-nio-8080-exec-21 url: /secure/CreateIssueDetails.jspa; user: mazafaka WARN mazafaka 1344x1086x1 587yrj 192.168.216.18,127.0.0.1 /secure/CreateIssueDetails.jspa [c.a.jira.index.AccumulatingResultBuilder] com.atlassian.jira.search.exception.InvalidDocumentFieldException: Document contains invalid fields [customfield_12200]

2026-03-25 22:24:40,529+0200 http-nio-8080-exec-21 url: /secure/CreateIssueDetails.jspa; user: mazafaka WARN mazafaka 1344x1086x1 587yrj 192.168.216.18,127.0.0.1 /secure/CreateIssueDetails.jspa [c.a.j.issue.index.DefaultIssueIndexer] No issues to replicate: numberOfCommentsToReplicate: 0, numberOfWorklogsToReplicate: 0, issueIndexingParams: {indexIssues=true, indexChangeHistory=true, indexComments=false, indexWorklogs=false}, performCounter: 1

2026-03-25 22:24:40,532+0200 http-nio-8080-exec-21 url: /secure/CreateIssueDetails.jspa; user: mazafaka ERROR mazafaka 1344x1086x1 587yrj 192.168.216.18,127.0.0.1 /secure/CreateIssueDetails.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:

Marc -Devoteam-
Community Champion
March 26, 2026

HI @Tony Montana 

I can't seem to find any related to this.

You could create a HAR file an raise this to scriptrunner or Atlassian support, as there are major changes when using Jira 11, that might need to be done, based on different Java version.

Also the field seems to be working, as you get results, but ticket creation fails. and this is the only error

DEPLOYMENT TYPE
SERVER
VERSION
11.3.3
TAGS
AUG Leaders

Atlassian Community Events