Forums
Home Product Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Get an error on creation any issue "We can't create this issue for you right now"

Alex Pogan
Alex Pogan December 21, 2019

It happens on creation every issue

there are some records about "com.idalko.jira.plugins.igrid.providers" but issues don't have any custom fields from Table Grid Editor  (but in common TGE plugin is used)

 

Can anybody help with that?

 

Messages in the log file

 

[c.a.j.bc.issue.DefaultIssueService] Error creating issue: 
com.atlassian.jira.exception.CreateException
	at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588)
	at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494)
	at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:192)
	at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:238)
	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:729)
	... 15 filtered
	at com.idalko.jira.plugins.igrid.WebResourceIncludeFilter.doFilter(WebResourceIncludeFilter.java:166)
	... 36 filtered
	at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62)
	... 12 filtered
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
	... 58 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)
	... 36 filtered
	at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
	... 5 filtered
	at com.idalko.jira.plugins.igrid.servicedesk.ServletRequestContextFilter.doFilter(ServletRequestContextFilter.java:23)
	... 8 filtered
	at com.atlassian.jwt.internal.servlet.JwtAuthFilter.doFilter(JwtAuthFilter.java:32)
	... 3 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)
	... 23 filtered
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.jira.workflow.WorkflowException
	at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:768)
	at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:580)
	... 257 more
Caused by: java.lang.NullPointerException
	at com.idalko.jira.plugins.igrid.providers.DataUtils.getOptions(DataUtils.java:694)
	at com.idalko.jira.plugins.igrid.providers.hibernate.DataSourceProvider.getDynItems(DataSourceProvider.java:328)
	at com.idalko.jira.plugins.igrid.providers.AbstractDataProviderImpl.getDynItems(AbstractDataProviderImpl.java:163)
	at com.idalko.jira.plugins.igrid.grid.type.ListColumnType.populateQueryProperties(ListColumnType.java:140)
	at com.idalko.jira.plugins.igrid.grid.type.ListColumnType.applyType(ListColumnType.java:94)
	at com.idalko.jira.plugins.igrid.grid.column.ColumnBuilder.buildColumn(ColumnBuilder.java:322)
	at com.idalko.jira.plugins.igrid.grid.column.ColumnBuilder.build(ColumnBuilder.java:216)
	at com.idalko.jira.plugins.igrid.grid.column.ColumnBuilder.build(ColumnBuilder.java:185)
	at com.idalko.jira.plugins.igrid.grid.GridBuilderImpl.build(GridBuilderImpl.java:243)
	at com.idalko.jira.plugins.igrid.grid.GridBuilderImpl.build(GridBuilderImpl.java:227)
	at com.idalko.jira.plugins.igrid.customfield.TableGridFieldManager.getGrid(TableGridFieldManager.java:395)
	at com.idalko.jira.plugins.igrid.customfield.TableGridFieldManager.saveChanges(TableGridFieldManager.java:190)
	at com.idalko.jira.plugins.igrid.customfield.AbstractTableGridCFType.createValueInternal(AbstractTableGridCFType.java:459)
	at com.idalko.jira.plugins.igrid.customfield.TableGridCFType.createValue(TableGridCFType.java:79)
	at com.idalko.jira.plugins.igrid.customfield.TableGridCFType.createValue(TableGridCFType.java:43)
	at com.atlassian.jira.issue.fields.ImmutableCustomField.createValue(ImmutableCustomField.java:693)
	at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:81)
	at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:1014)
	at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407)
	at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:606)
	at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:742)

 

 

 

Answer
Watch
Like Be the first to like this
992 views

2 answers

0 votes
francis
francis
Atlassian Partner
December 21, 2019

Hello,

 

 

Looking at the stacktrace

 

Caused by: java.lang.NullPointerException
 at com.idalko.jira.plugins.igrid.providers.DataUtils.getOptions(DataUtils.java:694)
 at com.idalko.jira.plugins.igrid.providers.hibernate.DataSourceProvider.getDynItems(DataSourceProvider.java:328)
 at com.idalko.jira.plugins.igrid.providers.AbstractDataProviderImpl.getDynItems(AbstractDataProviderImpl.java:163)
 at com.idalko.jira.plugins.igrid.grid.type.ListColumnType.populateQueryProperties(ListColumnType.java:140)

 

The grid tries to get the options of a dropdown column but bumps into a nullpointer exception.

 

Please raise an issue on our support portal, with the details of this issue, the version (+ family) of the table grid editor in use, and the version (+ family) of the jira

[family is something like jira software ...]

View More Comments
Alex Pogan
Alex Pogan December 22, 2019

Thanks for your reply

 

raised an issue

https://support.idalko.com/servicedesk/customer/portal/5/SOLV-3960

 

According to log it looks like the grid tries to get the options of a dropdown column. But why? there are no TGE custom fields on screens of issues we are creating

Like
francis
francis
Atlassian Partner
December 22, 2019

Can you check all the table grid editor custom fields and make sure that the custom field context is limited to the projects where you are using the custom field.

Like
Alex Pogan
Alex Pogan December 22, 2019

frankly speaking, most of TGE custom fields have global context (all issues, all projects)

but they are used only at specific project screens

what does global context mean ? I'm not very good at understanding how it works.

Are custom fields initialised if they are not on screens ? 

 

Are there any ways to switch on extra logging for idalko in JIRA to get more details on the problem? To understand what custom field bumps into a nullpointer exception.

Like
francis
francis
Atlassian Partner
December 22, 2019

Global context means that the custom field is available for all projects and issuetypes.

Whenever you initialise the grid, it will be initialised for all the issues that are being created - even when not on a screen.

 

Can I advice you to work with an Atlassian Certified Professional.  They will be able to point you in the right direction.  There is a cost associated (in most cases), but it is a good learning experience.

Like
Alex Pogan
Alex Pogan December 24, 2019

@francis Thanks a lot

You gave me a clue

I've checked all the TGE custom fields. I've found one that contains another single option CF with a wrong ID as a source for a column. As a result, it was a crash on creation every issue type because of an error on TGE CF initialization.

So we made a mistake in the script for a TGE custom field default value. But it was hard to understand the cause of the problem because of a lack of details in logs.

Like
francis
francis
Atlassian Partner
December 25, 2019

Yup - understood.

It is one of the reasons why we started with the table grid next generation - simplify the configuration.

 

Is it solved now?

Like
Alex Pogan
Alex Pogan December 25, 2019

Solved

Like
Reply
0 votes
Andrew
Andrew
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.
Get recognized
December 21, 2019

Hi

 issues don't have any custom fields

Are You sure? The custom fields are associated with issue through Screen schemes and through 'custom field' configuration.

Could You please check that the idalko field not used in the screens (check also screen in workflow transition) and in 'custom fields' panel?

B.R.

View More Comments
Alex Pogan
Alex Pogan December 22, 2019

Yes, unfortunately, I'm sure.

There are no Table grid editor custom fields on screens or workflow transition.

It seems that some idalko custom field is initialized. But why?

 

The problem occurs on every issue type. So we can't create any issue now.

P.S. Cloning works well.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Terms Security
    Welcome illustration

    Welcome to the new Atlassian Community

    Online forums and learning are now in one easy-to-use experience.

    By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.