Child pages
  • Sprint Marker Migration Fails after Upgrade due to invalid number error
Skip to end of metadata
Go to start of metadata


After upgrading JIRA Agile, some rapid board backlogs are not accessible. An error similar to the one below is displayed:

The following appears in the atlassian-jira.log

2015-06-18 14:01:22,465 JiraTaskExectionThread-1 ERROR admin 841x1965x1 josoa4 /rest/greenhopper/1.0/migration/sprintmarkers [service.migration.sprintmarker.SprintMarkerMigrationTask] 'EpicName' is an invalid number
com.atlassian.jira.issue.customfields.impl.FieldValidationException: 'EpicName' is an invalid number
        at com.atlassian.jira.issue.customfields.converters.DoubleConverterImpl.getDouble(
        at com.atlassian.jira.jql.query.AbstractNumberOperatorQueryFactory.getIndexValues(
        at com.atlassian.jira.jql.query.NumberEqualityQueryFactory.createResult(
        at com.atlassian.jira.jql.query.NumberEqualityQueryFactory.createQueryForMultipleValues(
        at com.atlassian.jira.jql.query.GenericClauseQueryFactory.getQuery(
        at com.atlassian.jira.jql.query.NumberCustomFieldClauseQueryFactory.getQuery(
        at com.atlassian.jira.jql.query.ContextAwareQueryVisitor.visit(
        at com.atlassian.jira.jql.query.ContextAwareQueryVisitor.visit(
        at com.atlassian.query.clause.TerminalClauseImpl.accept(


Diagnostic Steps

According to the error in the log excerpt above:

  • JIRA is trying to convert a custom field value ('EpicName') to a number but is unable to.
  • This exception is happening while trying to parse a JQL query (the board filters).

Using the SQL query below, you may find all JQL filters referencing with the 'EpicName' string value mentioned in the error:

Query 1
SELECT * FROM searchrequest 
WHERE reqcontent LIKE '%EpicName%';


The error is caused by a user custom field named as a JIRA Agile custom field (in this specific case, the Epic Link field).

Using the SQL Query 1 above, you can retrieve the JQL filter and also the custom field referencing the value displayed in the error message:

project = "Test Project" AND (Project_Name = PROJX OR "Epic Link" in (EpicName, EpicName2)) AND (...) 

Using the SQL query below, we can find all custom fields with the name "Epic Link":

Query 2
SELECT id, customfieldtypekey, cfname 
FROM customfield 
WHERE cfname = 'Epic Link';
  id   |                   customfieldtypekey                    |  cfname
 34572 | com.atlassian.jira.plugin.system.customfieldtypes:float | Epic Link
 30772 | com.pyxis.greenhopper.jira:gh-epic-link                 | Epic Link
(2 rows)


Renaming or deleting the duplicated custom field should resolve the problem.

For more information about how to perform these tasks, please refer to the Configuring a Custom Field document.

Help us improve!
  • No labels