Jelly Script Fails to Run as Service Throwing 'Could not parse Jelly script' Errors
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When running a Jelly Service, the following error appears in the atlassian-jira.log:
1
null:-1:-1: <null> Could not parse Jelly script
Cause
The xml tag is not closed, or the xml document is invalid.
Resolution
The problem can be solved by adding the closing tag to the login tag as follows:
1
<jira:Login username="user" password="password"/>Was this helpful?