Cannot create issue after adding Scripted field.

siva October 7, 2019

Not able to create issues after adding Scripted field in Script runner.

(After changing search template to (DATE TIME RANGE PICKER)

 

throws an error ::
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

 

( I have added a scripted field to script runner for checking dates. ) 

EVEN A DUMMY SCRIPTED FIELD IS BLOCKING WHEN ( date time range picker is selected)

any suggestions where to look.

3 answers

1 vote
Ravi Sagar _Sparxsys_
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 Leaders.
October 7, 2019

Hi @siva 

Did you try creating issues after removing the scripted field from the view screen? It seems like some problem with the post function.

Also share your scripted field code if you want.

Ravi

siva October 7, 2019

@Ravi Sagar _Sparxsys_ 

 

Yes , and im able to create. when i change the 

date time range picker to free text searcher .

 

and i get the error code.

========

2019-10-07 12:19:52,625 http-nio-8080-exec-3 ERROR john.wick 739x1634690x8 94sjbp 10.224.56.3 /secure/CreateIssueDetails.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: 
com.atlassian.jira.exception.CreateException: Indexing completed with 1 errors
 at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:600)
 at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:501)
 at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:193)
 at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:249)
 at com.atlassian.jira.web.action.issue.CreateIssueDetails.createIssue(CreateIssueDetails.java:99)
 at com.atlassian.jira.web.action.issue.CreateIssueDetails.doExecute(CreateIssueDetails.java:78)
 ... 1 filtered
 at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
 ... 7 filtered
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
 ... 15 filtered
 at com.softwareplant.ppm.structure.hostplatform.jiraserver.event.JiraServerIssueLinkFilter.doFilter(JiraServerIssueLinkFilter.java:52)
 ... 36 filtered
 at com.atlassian.servicedesk.internal.web.ExternalCustomerLockoutFilter.doFilter(ExternalCustomerLockoutFilter.java:55)
 ... 4 filtered
 at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62)
 ... 7 filtered
 at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:31)
 ... 4 filtered
 at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)
 ... 8 filtered
 at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
 ... 62 filtered
 at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
 ... 1 filtered
 at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
 ... 39 filtered
 at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
 ... 5 filtered
 at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.lambda$invokeFilterChain$0(CustomerContextSettingFilter.java:221)
 at com.atlassian.servicedesk.internal.api.util.context.ReentrantThreadLocalBasedCodeContext.rteInvoke(ReentrantThreadLocalBasedCodeContext.java:136)
 at com.atlassian.servicedesk.internal.api.util.context.ReentrantThreadLocalBasedCodeContext.runOutOfContext(ReentrantThreadLocalBasedCodeContext.java:89)
 at com.atlassian.servicedesk.internal.utils.context.CustomerContextServiceImpl.runOutOfCustomerContext(CustomerContextServiceImpl.java:47)
 at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.outOfCustomerContext(CustomerContextSettingFilter.java:212)
 at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilterImpl(CustomerContextSettingFilter.java:135)
 at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilter(CustomerContextSettingFilter.java:124)
 ... 4 filtered
 at com.atlassian.jwt.internal.servlet.JwtAuthFilter.doFilter(JwtAuthFilter.java:37)
 ... 8 filtered
 at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
 ... 4 filtered
 at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
 ... 26 filtered
 at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
 ... 25 filtered
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
0 votes
siva October 7, 2019

Yes i have only used it in View screen only,

 

when i select date time , not able to create issue.file server.PNG

Date Time Range picker Searcher
0 votes
Jack Nolddor _Sweet Bananas_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
October 7, 2019

Hi siva,

It seems you customfield is throwing a kind of exception, do you mind to look for it in either the atlassian-jira.log file or in the Script Runner's Scripted Fields section?

Log file location
The logs are written to the log subdirectory of your Jira application home directory (or elsewhere if you have configured a different location). You can view the location of the atlassian-jira.log in the 'File Paths' section of the system information page.


Regards

siva October 7, 2019

@Jack Nolddor -Sweet Bananas- 

 

You must to use Date Time Template
* You must to use Date Time Range picker Searcher

i have selected Date Time Template.

 

But When Date Time range picker serarcher im not able to create issues. 

 

no logs are added, how do i enable this so i can check where the issue is .

LOG.PNG

 

 

Jack Nolddor _Sweet Bananas_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
October 7, 2019

Please could you provide us the error thrown in the log files? To see what the problem is.

Anyway, an Scripted Field should be used only on View Screens, Do make it sense to have it in the Creation screen as well?

Suggest an answer

Log in or Sign up to answer