Here we’ve gathered the most common issues with the way how to troubleshoot them, and possible solutions.
Problem | Probable Cause | Possible Solution | |||
---|---|---|---|---|---|
1 | Not able to add new checklist items. Here is what is logged in the browser consolde
| This error can happen anytime the database user has not be granted the needed permissions, and JIRA is expected to create a new foreign key constraint. Explained here | Grant proper permisisons to Jira User by executing SQL command
Note: you can use 3rd party addon, like Database Explorer in order to execute these queries | ||
2 | Checklist statuses are not available | Conflict with settigns left after prevous version of Smart Addon that was installed on this instance |
| ||
3 |
message appears when trying an import checklist from a Template Jira version 8.12 | Known bug introduced by Atlassian in Jira v 8.12 Fixed in Jira 8.12.3, 8.13.1 More details: https://jira.atlassian.com/browse/JRASERVER-71747 | Upgrade your Jira to 8.12.3, 8.13.1 or higher version. | ||
4 | Checklist item could not be added. The following error shown in Jira log:
Reproduced on
| MySQL DB was not set properly | Check if mysql DB has set as suggested by Atlassian: https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-mysql-5-7-966063305.html Especially
| ||
5 | Using “Clone” Issue doesn’t copy “Checklists” field content to the newly created issue. | “Checklists” field is not added to the Projects, where Clone operation is executed. |
Note: For users who started using checklist fro m version 5.5.0 that should already been fixed. |
How can you help a team to better troubleshoot an error
...
Open Browser Console Log and make a screenshot of errors
In your Chrome browser, click and then More tools > Developer tools (F12)
Click the Console tab.
Refresh the page with Jira issue and checklist opened
to check for any errors in the console and send them to us as screenshots or screencasts
Generate.HAR file following these instructions from Atlassian and send to us.
...
In order to enable debug logging please follow below steps:
Navigate to Settings > System > Logging and Profiling
Find the Default Loggers section
Click the Configure button
Add
com.railsware.service.TemplateService
package withDEBUG
logging levelAdd
com.railsware.service.ChecklistService
package withDEBUG
logging levelCheck that you have templates with different trigger types
Once template was applied automatically to an issue check the
atlassian-jira.log
file
Book a Support or Demo session
...
Choose a proper area, a suitable time slot, and book a call. Our team will be happy to help you!
Insert excerpt | |||||||||
---|---|---|---|---|---|---|---|---|---|
|