Seeing "$projectKeyEncoded cannot be resolved" in JIRA debug logs when open any page. Why? Edited

With the JIRA logging set to DEBUG (on our development instance, to note), I'm now seeing around 10 of these debug statements in a row each time I refresh a page, basically.  In an effort to clean up the logs and help understand if there's something gone wrong, what could be causing this output?

2017-05-04 12:28:23,049 http-nio-8080-exec-6 DEBUG jira 748x4769x1 1vm87zx xx.xxx.xx.xxx /secure/MyJiraHome.jspa [velocity] Null reference [template 'getEncodedBodyFromContent', line 1, column 33] : $projectKeyEncoded cannot be resolved.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

649 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you