Troubleshooting
This guide helps you resolve common issues with Simple Risk Register. If your issue isn’t covered here, contact support.
Installation and access issues
I cannot see Risk Register in the project sidebar
Symptoms: The “Risk Register” menu item doesn’t appear in the project navigation.
Solutions:
-
Verify installation
- Go to Jira Settings (⚙️) → Apps → Manage apps
- Search for “Simple Risk Register”
- Confirm it shows as “Enabled”
-
Check project permissions
- Ensure you have “Browse Projects” permission in the project
- Try a different project where you have access
-
Wait and refresh
- Wait 2-3 minutes after installation
- Refresh the browser page
- Clear browser cache if needed
-
Check app restrictions
- Ask your Jira admin if app access is restricted
- Some organizations limit apps to specific projects or groups
I cannot see the Related risks issue panel
Symptoms: The “Related risks” panel doesn’t appear on issue view.
Solutions:
- Enable Related Risks panel: Click the gear icon right below the issue summary field and select the Related Risks menu item
- Refresh the page - The panel may need a refresh to appear after installation
- Check issue view layout - Custom layouts may hide panels; try the standard view
- Verify installation - Confirm the app is installed and enabled
- Check permissions - Ensure you can view the issue
”Project context not available” error
Symptoms: Error message saying project context is not available.
Cause: The app cannot determine which project you’re in.
Solutions:
- Access from project context - Always open the app from within a project (not from a bookmarked URL)
- Refresh the page - If you navigated directly, refresh to reload context
- Use the sidebar - Navigate via the project sidebar “Risk Register” link
Risk management issues
I cannot create a risk
Symptoms: Create button doesn’t work or shows an error.
Solutions:
- Check required fields - Title is required; ensure it’s filled
- Check field lengths - Title max 200 chars, Description/Mitigation max 1000 chars
- Check status value - Must be Open, Mitigated, or Closed
- Check probability/impact - Must be values 1-5
I cannot assign an owner
Symptoms: Owner dropdown is empty or doesn’t show the user I want.
Cause: The owner list comes from assignable users in the project.
Solutions:
- Verify user is active - The user must have an active Jira account
- Verify project access - The user must have access to the current project
- Check assignability - The user must be assignable in the project (check project roles)
Risk score isn’t what I expected
Symptoms: Score doesn’t match probability × impact.
Solutions:
- Check values - Score = Probability × Impact (e.g., 3 × 4 = 12)
- Refresh the page - Display may need a refresh to update
I cannot edit a risk
Symptoms: Edit button doesn’t work or changes don’t save.
Solutions:
- Check network connection - Changes require connectivity
- Check field validation - Ensure all values are valid
- Try again - Temporary issues may resolve on retry
Issue linking issues
Linked issue search shows no results
Symptoms: Searching for issues returns empty results.
Solutions:
- Check project scope - Issues must be in the same project
- Check search term - Try searching by issue key (e.g., “PROJ-123”)
- Check issue visibility - You must have permission to view the issue
- Check limit - Only recent 100 issues are searchable
”Issue already linked” error
Symptoms: Cannot link an issue that’s already linked.
Solution: Each issue can only be linked once to a given risk. Check the Linked Issues section to see if it’s already there.
Linked issue shows wrong information
Symptoms: Issue details (status, assignee) are outdated.
Cause: Linked issue metadata is cached from when the link was created.
Solution: Unlink and re-link the issue to refresh its metadata.
Import and export issues
CSV import failed completely
Symptoms: No risks were imported from the CSV file.
Solutions:
- Check file format - Must be a
.csvfile - Check headers - Required headers: Title, Description, Status, Probability, Impact, Mitigation
- Check encoding - Use UTF-8 encoding
- Check for BOM - Remove byte order mark if present
Some rows failed to import
Symptoms: Import partially succeeded with errors.
Solutions:
- Review error messages - Check which rows failed and why
- Check validation rules:
- Title required, ≤200 characters
- Description ≤1000 characters
- Status must be: open, mitigated, closed (lowercase)
- Probability/Impact must be: 1, 2, 3, 4, 5
- Fix and re-import - Correct the failed rows and try again
Export is empty or missing risks
Symptoms: Exported CSV has fewer risks than expected.
Solutions:
- Check filters - “Export Filtered” respects current filters
- Use “Export All” - This ignores filters
- Verify risks exist - Check that the project has risks
Drag and drop issues
Drag and drop doesn’t update a risk
Symptoms: Dragging a risk to a new cell doesn’t save the change.
Solutions:
- Refresh the page - Try refreshing and dragging again
- Check connectivity - Network issues can prevent saves
- Verify risk exists - The risk may have been deleted by another user
- Watch for rollback - Failed updates may animate back to original position
Risk jumps back after drag
Symptoms: Risk moves but then returns to original position.
Cause: The update failed (network issue, validation error, or concurrent edit).
Solutions:
- Check for errors - Look for toast notifications
- Refresh and retry - The risk may have been modified by someone else
- Try editing instead - Use the edit form to update probability/impact
Display issues
Heatmap appears empty but risks exist
Symptoms: Table shows risks but heatmap appears empty.
Solutions:
- Check filters - Filters apply to both views
- Scroll - Risks may be in different cells
- Refresh the page - Display may need a refresh
Issue panel says “No risks linked”
Symptoms: Related risks panel shows empty even though risks should be linked.
Solutions:
- Verify links - Check the risk register to confirm the issue is linked
- Check project - Issue and risks must be in the same project
- Refresh the issue - Page may need a refresh to show updated links
Performance issues
App is slow to load
Solutions:
- Check network - Slow connection affects load time
- Clear cache - Clear browser cache and cookies
- Try incognito - Test in incognito/private mode
- Check Jira status - Jira itself may be experiencing issues
Changes take time to appear
Cause: Changes are saved immediately but display may lag.
Solution: Refresh the page if changes don’t appear after a few seconds.
Escalation and support
When to contact support
Contact support if you experience:
- Data loss or corruption
- App not loading
- Features not working as documented
- Errors that persist after troubleshooting
Information to include
When contacting support, provide:
| Information | Example |
|---|---|
| Jira site URL | yourcompany.atlassian.net |
| Project key | PROJ |
| App version | v1.2.3 (from footer) |
| Issue description | Clear description of the problem |
| Steps to reproduce | 1. Open app 2. Click X 3. Error appears |
| Screenshots | Visual evidence of the issue |
| Browser/version | Chrome 120, Firefox 121 |
| Time of occurrence | 2024-01-15 14:30 UTC |
Support channels
- Support portal: https://small-batch.atlassian.net/servicedesk/customer/portal/34
- In-app links: Use footer links for quick access