Jira sub tasks issue - giving error

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

4 answers

1 accepted

4 votes

Answer accepted

Hi All,

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?

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;

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;

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.

Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

select count(*) from issuelink where sequence IS NULL;

returns to me 1442

so i should run

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

1442 times for every linktype that DDL "select * from issuelink where sequence IS NULL;" displayed for me ?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello Alex

You have run below query

select * from issuelink where sequence IS NULL;

After executing, you will be seeing the duplicate numbers in 'linktype' column.

Then you have to run 'UPDATE' query

UPDATE issuelink SET sequence = 0 WHERE linktype= {paste the duplicate number} AND sequence IS NULL;

By executing above query, it will eliminate the duplicate values. You have to keep running till the count to be shown as '0'

After that, please restart JIRA and you will be seeing all the sub-tasks

Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • like this

Yes! That's more understandable, it works like a charm without any restart! Thanks!

One issue here that is left - when user was mention another user i see accountuseerid:... how can i fix it ? it's trying to locate such ID by a new path (after we moved from cloud to server)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I am also facing the same issue.

Please try to add 'users' in user management with apt permissions and check if that fixes the issue.

Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you so much, @polavarapu venugopal

Your suggestion above works.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

set sequence = 0
Could you explain why this particular value? I don't want it to be magic.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Download this app Cloud Compatibility for Jira when user was mention another user i see accountuseerid:...

https://marketplace.atlassian.com/apps/1221117/cloud-compatibility-for-jira?hosting=datacenter&tab=overview

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Amazing! Thanks!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Ran into the same problem after an import of subtask links.

Managed to rectify the corruption by using issueLinkManager.resetSequences method (https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/issue/link/IssueLinkManager.html#resetSequences-java.util.List-).

Here is a snippet:

def links = issueLinkManager.getOutwardLinks(issue.id)?.findAll { it.issueLinkType.name == "jira_subtask_link" }
issueLinkManager.resetSequences(links)