• Community
  • Products
  • Jira Software
  • Questions
  • I am getting 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

I am getting 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

Alejandro Briceño August 22, 2016
 

3 answers

5 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 22, 2016

Two things

First, check over what you're putting into the issue - does it have special characters or unusual content in it?  (e.g. accented characters, text in a language that you don't usually use, or emojis, for example).  Can you create issues without any special content?

Second, can you read the log file and see if there are errors appearing in that at the time at which you click "create"?

Alejandro Briceño August 22, 2016

HI nic, 

I checked the first and we do not use special contents.

 

I checked the log file it has to be with  a post function using the script runner add on :/ I was using a trial version of that add on, but i alredy unistalled 

Like Gergo Kiss likes this
Alejandro Briceño August 23, 2016

Problem Solved

 

Thank you NIC!!!!!!

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 23, 2016

Did you remove the post-function before you un-installed script-runner?  Depending on the version, you might still be able to remove it, but a post-function that tries to use add-ons that have been removed can easily block transitions from working.

Prasad Andrews February 5, 2019

Hi, @Nic Brough -Adaptavist- - Please suggest me how do I fix this?

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.

First, I have checked over what am putting into the issue description and summary - it has special characters because the user is from Spain (Spanish) accented characters,

I am unable to create the issue via mail handler and manual as well.

Second, dig the log file and read the log file and see the below errors appearing at the time of click "create"?

Note: I have small doubt when we install JIRA application by default Spanish language addon also installed but we have configured the default language is English.

So please suggest us, some Spanish users, also using JIRA and there are sending mail to particular DL so automatically JIRA issue will create as we are using mail handlers.

How do I fix this issue? 

LOG: 

2019-02-05 05:21:38,707 http-nio-8080-exec-782 ERROR Prasad.EDA 321x19088520x1 qy2oqr 10.255.248.254 /secure/CreateIssueDetails.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:
com.atlassian.jira.exception.CreateException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Actualizaci?n sistemas GIS][watches,0][creator,prasad.eda][created,2019-02-05 05:21:38.697][timespent,null][timeoriginalestimate,null][project,12516][description,Create a ticket for the strategy of LLA GIS

VTR has a tactical situation regarding to uograde what they have or we look towards a LLA GIs system.
________________________________________________________________________________________________________________
The information contained in this transmission is confidential and proprietary and it cannot be used by any person other than its addressee(s). Unauthorized use of the information contained in this transmission in any form may be punished under Chilean Law and be considered a copyright, industrial property or trade secrets infringement. If received in error, please destroy it and notify the sender by calling collect or e-mail. As there can be no certainty that this message will not be modified as a result of its transmission via e-mail, VTR Globalcom.S.A. shall not be responsible if the content of the same has been modified. Visit vtr.com
][reporter,prasad.eda][type,11107][priority,3][number,28941][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,prasad.eda][id,1045036][updated,2019-02-05 05:21:38.697][workflowId,1128128][status,10908] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1))
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)
... 52 filtered
at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62)
... 7 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:80)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:78)
... 36 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
... 10 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)
... 29 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
... 28 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: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Actualizaci?n sistemas GIS][watches,0][creator,prasad.eda][created,2019-02-05 05:21:38.697][timespent,null][timeoriginalestimate,null][project,12516][description,Create a ticket for the strategy of LLA GIS

VTR has a tactical situation regarding to uograde what they have or we look towards a LLA GIs system.

_______________________________________________________________________________________________________________________

][reporter,prasad.eda][type,11107][priority,3][number,28941][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,prasad.eda][id,1045036][updated,2019-02-05 05:21:38.697][workflowId,1128128][status,10908] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1))
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:767)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:580)
... 252 more
Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Actualizaci?n sistemas GIS][watches,0][creator,prasad.eda][created,2019-02-05 05:21:38.697][timespent,null][timeoriginalestimate,null][project,12516][description,Create a ticket for the strategy of LLA GIS

VTR has a tactical situation regarding to uograde what they have or we look towards a LLA GIs system.
_______________________________________________________________________________________________________________________

][reporter,prasad.eda][type,11107][priority,3][number,28941][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,prasad.eda][id,1045036][updated,2019-02-05 05:21:38.697][workflowId,1128128][status,10908] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1))
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:299)
at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:172)
at com.atlassian.jira.entity.EntityUtils.createValue(EntityUtils.java:35)
at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:1150)
at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:72)
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:741)
... 253 more
Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Actualizaci?n sistemas GIS][watches,0][creator,prasad.eda][created,2019-02-05 05:21:38.697][timespent,null][timeoriginalestimate,null][project,12516][description,Create a ticket for the strategy of LLA GIS

VTR has a tactical situation regarding to uograde what they have or we look towards a LLA GIs system.
_______________________________________________________________________________________________________________________

][reporter,prasad.eda][type,11107][priority,3][number,28941][environment,null][security,null][timeestimate,null][duedate,null][resolutiondate,null][votes,0][assignee,prasad.eda][id,1045036][updated,2019-02-05 05:21:38.697][workflowId,1128128][status,10908] (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1))
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:213)
at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:178)
at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:83)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:556)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:542)
at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:97)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:296)
... 261 more
Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:683)
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:205)
... 267 more
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect string value: '\xEF\x83\xA8 1 ...' for column 'DESCRIPTION' at row 1
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4118)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2794)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2375)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2359)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:673)
... 268 more

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 5, 2019

In this case, it's not Spanish that's the problem.

You are using MySQL as the backend database and that does not support the higher-numbered emojis (and some other characters).  Remove the emojis from the text and try again.

Like Espen Vien likes this
Prasad Andrews February 5, 2019

@Nic Brough -Adaptavist- - Thank you Soo much now I removed emojis from the text.

 

Regards,

Prasad

anshu02
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.
March 25, 2019

Hi @Nic Brough -Adaptavist- 

I am facing the same error, i tried checking atlassian-jira.log but it shows indexing errors, any thoughts over this.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 26, 2019

Emoji's can cause indexing errors.  But if it's not showing you a string that translates into an emoji, you are going to need to explain what errors you are seeing.

Thomas Bithell April 10, 2019

We have seen Microsoft emojis from Outlook or Word cause this problem many times. It also causes this error within Confluence "Error: Unable to communicate with server. Saving is not possible at the moment."

Chris Buzon
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.
August 19, 2020

@Nic Brough -Adaptavist-  thank you again for answering so many questions.  This exact problem came up for one of my teams today, and your answer was correct again.

1 vote
Chris Buzon
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.
August 19, 2020

Thanks to Nic for his explanations. 

This scenario came up with one of my teams today. It was not exactly the same situation, but it did turn out that the value one of the post-functions was trying to set was changed by someone else on another project, making the post-process fail (since it was trying to write an unsupported value to a custom field).  I just needed to update the post-function with the new value(s) for that custom field and we were back in business.


0 votes
oneumyvakin August 23, 2018

I've got this issue when tried to set "Summary" field which exceed 191 characters.

Suggest an answer

Log in or Sign up to answer