Symptoms
When attempting to take a new snapshot, you get an error message indicated indicating that the snapshot cannot be taken because due to an internal server error. A snapshot is not taken, and a new page version is not triggered.
How to solve this?
...
Solution
The internal server error is frequently arising from comes after Jira returning returns an error for the data request for data. Follow these steps to troubleshoot:
Find out (with With the help of your admin) , find out which user is configured has permission to perform the access to Jira and the retrieval of retrieve the snapshot. This is important because this user may have different view permissions than what you have when you access accessing Jira.
Verify that the user who is configured for access , can , perform an advanced search in Jira, perform advanced search using exactly the exact JQL clause that is configured in your snapshot. If this user gets an error when performing the advanced search in Jira with that user returns an error, this might be because, possible reasons are:
The JQL clause has an error.
The user has access restrictions that cause caused the JQL to fail (for example- they have . For example: the JQL clause has no errors, but the user has no access to a the project that is mentioned in a well-formed JQL)referenced in the JQL.
If the snapshot used to work but doesn’t work now stopped, this might may be because of due to changes in the Jira configuration. For example- , such as a change in custom field.
The JQL verification of JQL needs to be done for each of the levels that is configured in your macro. For Levels 2 and above, where you use a dependence which have dependencies on previous levels, replace try replacing the dependency with real data instead of the dependence: ie, replace $key with SPACE-334 . For example: replace “$key” with “SPACE-334” (or whatever is suitable relevant for your data), to check that at least the sytax syntax is correct.