Jira sub tasks issue - giving error

[polavarapu venugopal]

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

[Josh Steckler]

Hi Robert,

I found this, which may help on server but not for cloud. https://community.atlassian.com/t5/JIRA-questions/How-do-you-increase-the-bulk-change-maximum/qaq-p/417702

But if it were me, I would automate. I would write a script using the REST API that would run daily, deleting issues after a certain amount of time after closure.

[Ron Gates]

With ScriptRunner you can configure Escalation Service that can run periodically and remove all the issues found by defined JQL query - see the screenshot of example configuration:

Above example will run every 60 minutes and delete all the issues found by following query:

project = "Jira" AND Status in (Closed, Resolved)

Here is the script that performs delete using "silent" deleteIssueNoEvent method which is perfect for automated bulk deletes:

import com.atlassian.jira.component.ComponentAccessor
def issueManager = ComponentAccessor.getIssueManager();
issueManager.deleteIssueNoEvent(issue);

I tested above approach myself and it works.

[GaryM]

It works, the issue(s) get deleted, but atlassian-jira.log contains 2-lines of ERROR message for each issue deleted. (Jira 7.5.1) (ScriptRunner 5.2.1)

2017-11-08 01:07:01,166 Caesium-1-4 ERROR admin     [c.o.s.c.jira.utils.WorkflowUtils] Errors: {}
    Error Messages: [You can not update a null issue.]
2017-11-08 01:07:01,169 Caesium-1-4 ERROR admin     [c.o.s.c.jira.utils.WorkflowUtils] Not attmpting transition

Null Issue, I guess because it deleted and nothing to transition.

Any ideas to suppress the messages?

[Anja Nagel]

Hello,

we have exactly the same problem. The Escalation service works great, but still the messages are written to the log-file.
(Jira V8.8.1 ), (Scriptrunner 6.18.0)

Can the messages be turned off or ignored?

[Martin Runge]

It works perfectly and the issue(s) get deleted. Thanks josh!

[aas]

Does anybody know will it slow down jira if the result of JQL Query will 130K issues? May be there's some way to limit query result?  

[ArulAnthonySebastian Nadar]

Please use below code at Escalation service:

import com.atlassian.jira.component.ComponentAccessor
def issueManager = ComponentAccessor.getIssueManager();
issueManager.deleteIssueNoEvent(issue);

Note: If you use the Scriptrunner plugin, above code with escalation service will work.