Jira sub tasks issue - giving error after migrating the data from Jira cloud to Jira server

[Вячеслав Калашников]

After migrating the data from Jira cloud to Jira server, we have observed that for issuetype = 'subtask', the description field is giving below error message.

Kindly provide me your valuable suggestions

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.subtask.SubTaskSequenceColumnLayoutItem threw exception java.lang.NullPointerException: null value in entry: actualSequence=null at templates/jira/issue/table/macros.vm[line 117, column 34] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:342) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:507) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.Foreach.performIteration(Foreach.java:393) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:316) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:212) at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:247) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime

[Вячеслав Калашников · Accepted solution]

I solved the problem like this.

Atlassian recommended with the below solution which apparently fixed the issue. Please try it out from your end.

I have checked the information you provided and it appears that there is an inconsistency in your database.  Thank you for letting us know that you already ran the integrity checker and performed a re-index.

Currently the issue looks to be related to the issuelink table, can you please take the following steps?

1. First run this query to see if there are any null values in the table;

2.   3.  select count(*) from jiradb.issuelink where sequence IS NULL;

1. If the value is greater than 0 run the following command to retrieve the faulty lines: 

5.   6.  select * from jiradb.issuelink where sequence IS NULL;

1. Then adjust the following query where you take the value (here set as example to 10100) from the field LINKTYPE returned by the query in step 2 and run the update statement:

8.   UPDATE issuelink SET sequence = 0 WHERE linktype=10100 AND sequence IS NULL;

 Since the query involves running an update statement, Please ensure to make a native database backup before modifying the database and it is recommended to run the query on database connected to a test environment first before trying on the database connected with production instance.

[Brant Schroeder]

@Вячеслав Калашников Welcome to the Atlassian community

Looks like you have some broken data somewhere after doing your migration.  I would suggest:

• Logging in as an admin
• Run the integrity checker - You will want to run every single one and I would suggest doing them one at a time so you do not get a time out.
• Do a full re-index (No Background)- This will lock everyone out but it will get done more quickly to see if it fixed the issue.

If you are still having the issue afterwards you will need to review more of the logs to see if you can determine what the issue is.

[Вячеслав Калашников]

Hi. thanks for your answer.  integrity checker and full re-index did not help me

[Brant Schroeder]

@Вячеслав Калашников did you have any apps on cloud that are not on server?

[Вячеслав Калашников]

@Brant Schroeder yes, Epics Map for Jira and Issue Checklist Free

[Вячеслав Калашников]

@Brant Schroeder also i cant create sub-task, system returns me error

[Brant Schroeder]

I would suggest submitting a support issue to Atlassian but I would also try disabling the add-ons that are not in the server instance, creating a new export and seeing if that fixes the issue.